Just a note to tell the peeps that the second version of DebugObject is out.
http://dark-wire.com/products.php
This version has shared data across the application and catches unhandled exceptions (i.e. crashes) thrown by the MMF2 runtime and other extensions, and can either start an infinite sleep to wait for you to attach a debugger, pass control to a debugger automatically, continue the execution, etc.
Enjoy.
Nice! How did you manage to get it to catch thrown exceptions that are not part of your extension's call stack?
Working as fast as I can on Fusion 3
Because he's on the Dark side of the Net tfuu I meant Web. Anyway great extension SortaCore!
Where were you yesterday LB? I needed some help with that global data sharing, and all I had was 7 admins and a moderator gazing down at me. It was like death, but slower and with more CT staff. And less death.
Another update today folks, I replaced a few NULLs with references to actual variables, so global data sharing should actually be added.
Also, I am supplying the debug symbols with private symbols stripped. This means you can see the name of the function in DebugObject in the call stack that crashes if the actual object itself breaks, but none of the source code. It helps debugging objects considerably - for example, if DebugObject crashed on the "OpenFile()" function, you would know where to start, rather than "0x3FBBA21E()".
Microsoft actually supply these symbols for all their Windows DLLs (which are closed-source), and even host them on a dedicated set of servers, so anyone with Visual Studio can download them directly while debugging:
I'll be doing this for all of my objects starting from their next update. I hope Yves/Francois distribute the stripped debug symbols for the MMF2 runtime so we have a better idea of why edrt.exe is crashing when it does.
You can build stripped debug symbols the same way you build regular symbols, just use the box below the "Generate Program Database File", and put a different file name in. VS will build a stripped-info set of debug symbols. Make sure "Generate Debug Info" is set to Yes at the top, as well.
In the above example you can see that the kernel function that has paused the Gwerdy chatroom is a "WaitForObject" function. Much more helpful than "It's anything in Kernel32.dll".
hint, hint, Yves/Francios...
Hi SortaCore, (Phi now) !
Thanks for this amazing extension (I waiting so much for a thing of that kind)!
But.. I can't figure how using this... Can you write some documentations files, (or Example) and ship with next release?
Thanks one more time, you rocks!
The extension is semi-intuitive, but once it gets to a final release, there'll be help docs if I deem it not newbie-friendly.
What particular part is confusing you?
In fact .. all lol
No more seriously, I can't figure where I must start to debug with your extension, can you provide some samples ?
(Handles crash, Output) that's matter..
I can't make the things working (certainly because I take the wrong orders of actions...)
Help please
Okay, I recommend an order like thus:
Click to see full-size image.
That should get you working
I've experienced a crash using this object in Windows Server 2008 R2 64-bit; I am unable to find a suitable way to debug it, so the bug is most likely going to remain for a while.
Posting Permissions
Reply With Quote