.NET obfuscator and automated error reporting
Moderators: Luke Jefferson, melvyn.harbour, dom.smith
Sometimes it would be nice to be able to drill down through all the members and local variables in the reported stack trace. For instance, I received an error from a user that was caused by a member variable that is a class. This variable has other members that I would have liked to inspect. Right now the report shows whether the sub-member is null, or what type it is, but no other details (except for arrays).
I realize there may be tradeoffs between complexity, speed, and size of the error report. Perhaps we could include an attribute on classes or specific members that the report can drill down into?
- Posts: 16
- Joined: Mon Oct 06, 2008 5:08 pm
Thank you for your post!
I'm wondering if perhaps this might just be a case of needing to enable error reporting on the DLL containing the class you want to drill into?
My apologies if I'm misunderstanding the question, but if so.. do you think you could send an example application or example error report where the details are lacking? (you can send it to email@example.com
with f0075247 as the subject)
Red Gate Software Ltd.
- Posts: 235
- Joined: Mon Apr 23, 2012 1:13 pm
Return to SmartAssembly 6
Who is online
Users browsing this forum: No registered users and 0 guests