How to debug an obfuscated and merged assemblies.

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, Alex.Davies, melvyn.harbour

How to debug an obfuscated and merged assemblies.

Postby rtom » Thu Jun 17, 2010 4:48 am

After a set of assemblies where merged and obfuscated, the program will no longer run. Is it possible to debug obfuscated code. I attached a debugger to it, but the call stack is mangled. Is there an easy way to find out what is wrong, and were in the code this is happening

Thanks
rtom
 
Posts: 4
Joined: Thu Jun 17, 2010 4:42 am

Postby slaphead99 » Thu Jun 17, 2010 12:44 pm

Yes, absoultely- this is what the "self-diagnosis" mode is all about. Its like the local version of the unhandled exception reporting feature (which works just as well too - except there is the "middle-man" of report transmission). So just apply the self-diagnosis feature.
slaphead99
 
Posts: 92
Joined: Wed Mar 10, 2010 2:27 pm

Not having much success with smart assembly tool

Postby rtom » Thu Jun 17, 2010 2:37 pm

I have a fairly large project that brings in a large number of 3rd party assemblies. After obfuscation, I get error messages with funny character strings. These are likely related to messages with substituted strings.

I tried various Smart assembly options, to try and get my program to run after going through the tool. For example, I just reduced it to dependency merging and embedding and pruning and now my application no longer runs. Seems to be related to web service calls.

There must be a set of rules for exclusions that we can apply to ensure error messages are displayed properly. Any docs outlining best practices for obfuscation?
rtom
 
Posts: 4
Joined: Thu Jun 17, 2010 4:42 am


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests