PDA

View Full Version : Debugging a xenocode dumped assembly


tribal
05-19-2009, 03:59 AM
Hello,

I am having troubles with a recent assembly I started working on.
The assembly is protected and obfuscated with xenocode. I dumped all of the packed dotnet assemblys using with the generic unpacker which worked ok.

The application uses DeployLX Licensing for which I wrote a dummy dll file to bay-pass it. I patched the main executable so that it would except my dll.

The program is basically packed as follow by xenocode (all in the virtual filesystem):
Main executable
dotnet dll (written by the programmer)
Various 3rd party dll's

Now, If I run my dumped and patched exe all seems to be going fine exept for 1 function where it calculates some statistics. Somewhere along the line it gives (I think, I cant properly compare it with the original exe) an exception that should not accure. The calculation method used is stored in the dll and called by the main executable.

The problem I have is that I cant debug the thing. Its still obfuscated preventing me from dis/reassembeling it using il(d)asm. I tried dotnet tracer 0.4 to see if I could get a clear exception to point me in the right direction but all I see is that an exception is thrown and catched but I cant see any details from that exception. I also tried dile but dile simply hangs and crashes if I try to go into the disassembled code.

Can anyone point me in the right direction on how to proceed to find and fix the bug I have in my dumped files? Also, is it somehow possible to debug the untouched xenocode executable to log if there are any differences in the calls and exceptions?

Edit: If I dont patch the executable and use the normal deployLX licensing dll the same problem accures, so my own dll should be fine.

tribal
05-26-2009, 05:34 AM
Little bump ... no one with ideas about this?

Kurapica
05-26-2009, 10:34 AM
You should upload the files here first.

tribal
05-27-2009, 01:34 PM
Hm, for some reason it let me re-assemble the dll with il(d)asm resulting in a working version :confused: Never had any succes in re-compiling a xenocode fuckedup assembly but this time it worked...