Build 451 - decompile attempt (specific dll) crashes VSTS

Explore, browse and analyze .NET assemblies

Moderators: Luke Jefferson, Charles Brown, StephenC, Alex.Davies, Greg.Tillman, melvyn.harbour

Build 451 - decompile attempt (specific dll) crashes VSTS

Postby marc.gravell » Fri Oct 23, 2009 3:05 pm

Using Build 451 (was: 415, was: 381) on XP32/VSTS (2008).

I have a sample dll that I wanted to decompile (oddly enough, so I could re-compile it and use with source in ANTS) - it gets to 68% and then hard-crashes VSTS. (I repeated the attempt, just in case it was karma).

I can supply the dll on request. The dll is my own, and is not obfuscated. It is actually generated on-the-fly (CSharpCodeProvider) from data; I was simply trying to use Reflector to save myself the trouble of going in, turning on debug (so that it writes the cs to disk in addition to the dll), re-deploying and re-building the dynamic portion. I can supply the referenced dlls if needed, and the original cs if that would be helpful.
Last edited by marc.gravell on Thu Oct 29, 2009 10:58 am, edited 2 times in total.
marc.gravell
 
Posts: 14
Joined: Mon Oct 19, 2009 9:33 am
Location: UK

Postby Alex.Davies » Fri Oct 23, 2009 4:40 pm

Yes, I'd be really interested to get the assembly that causes that crash. I've sent you an email.

Thanks a lot,
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk

Postby marc.gravell » Fri Oct 23, 2009 8:43 pm

dll + project sent by e-mail
marc.gravell
 
Posts: 14
Joined: Mon Oct 19, 2009 9:33 am
Location: UK

Postby Alex.Davies » Tue Oct 27, 2009 12:28 pm

That was good fun to debug. Unfortunately, I'm not going to be able to fix it completely, as the function (the constructor of PCDataContext) is just too large, and causes a stack overflow. It's not worth rewriting to avoid the recursive walking the contents of the method, but I've put in something to avoid crashing VS completely. It'll be in the next build.

Thanks,
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk

Postby marc.gravell » Tue Oct 27, 2009 1:33 pm

That's fine; for insane code, simply reporting an error (rather than killing VSTS) seems reasonable. And yes: that generated code is pure evil, but great for test purposes ;-p
marc.gravell
 
Posts: 14
Joined: Mon Oct 19, 2009 9:33 am
Location: UK


Return to .Net Reflector 6.x and .NET Reflector 6.x Pro

Who is online

Users browsing this forum: No registered users and 0 guests