DebugObject now out - run events when your app crashes

[Phi]

Hey folks,
Ever hated it when your programs die unexpectedly and totally wreck your otherwise professional look? Or that when it crashes, it quits instantly and won't let you debug?

DebugObject (v5) now allows you to run events when your application crashes. Instead of the classic belly-flop when your program crashes, you can set it up to:

• Run another program to show a "Uhoh, your prorgam died, want to restart the program and/or send an email to the developers?" popup.
• Save files that need that last bit of information stored.
• Delete sensitive or temporary files.

Thanks to the cool coding behind DebugObject, not only will this handy extension catch any crash in the entire MMF2 runtime, but any crash within any of the extensions you're using in your program, too.

It features log output which can be switched on and off at runtime, an optional console where you can input debug commands, several methods of handling crashes, and ways to trigger crashes (useful for hack detectors).

The program comes with full documentation and an example file, showing DebugObject's capability.

Enjoy, and in case you missed the download link, here.

- Phi

[Ryan]

This sounds really handy. I'm quite keen to try the "Save files that need that last bit of information stored."

I'm curious, if your Save event is the event that causes the crash, any you re-run the save event on the crash, would it cause a hall-of-mirrors effect? Is the extension smart enough to pick up this kind of loop?

[Phi]

It can pick up on itself, but I haven't coded the extra 6 lines to stop-recursive-errors. I should probably do that soon.
The saving can't be multi-threaded, though. If it's the type that stalls MMF2 while it saves it's fine. But after the last "On unhandled exception" event finishes running its actions, the app insta-closes.

[happygreenfrog]

Woah! That sounds epic! Downloading it.

[BackStaged]

It's for which Runtime ?
(Windows, I think it's, but other ?)
By the way, Yippikayai!

[Phi]

New version supports detecting crashes if attempting to run the "on unhandled exception" events fails. It also supports minidump generation, which is essentially a copy of the environment that caused the crash which can be opened in Visual Studio at your leisure. You can set the minidump to be as detailed or basic as you want.

I've fixed the properties, bar the new-to-this-version one, which is buggy for the moment and so has been disabled.
The documentation has been repaired as well and the a/c/e's documented a bit more fully.
Finally, the support for handling the console has been increased significantly.

[BackStaged]

Thanks for that fantastic object Phi!
Also thanks for your answer !

Cheers!

EDIT:

In example file, I noticed that it there in place thoses events lines when we click on the : "Crash with DebugObject" button:
Cause crash: access violation (read)

So.. It's logic that we can handle THIS precise case of crash no?

Instead we can only set (and see) this condition for the DebugObject:
Unhandled exception trigger

AND no conditions to handle this precise trigger exception's case..
(a forget?)

It then will be useful to add some conditions like:
Custom Exception Trigger On "test1"

And then add actions like:
Cause crash: test1

It's my mind and perhaps an enhanced future feature for a future version !

Well, thanks to read at me!

[Phi]

I think what you want is a function object, they do the same thing, but unlike DebugObject they don't make the application quit once they're done executing.
If you don't want to use an extension, you could use a fastloop running once.

However, I think there should be some expressions for retrieving information about the crash when it happens. Just make sure you read the help file, under the "On Unhandled Exception" condition.

[NecroLuigi]

Hello, Phi! First of all, AWESOME extension, thanks and congrats!

Would you happen to have somewhere a download link for the previous 2 or 3 releases of this extension? We have been using it in The Journey of Eko and recently had to reinstall MMF. I downloaded all the needed extensions, but I'm still unable to open the mfa for the game - MMF says it's lacking debugobject.mfx. I then reinstalled Debug Object directly from your link (instead of Extension View), and also directly from your site, but no luck... The funny thing is that I know the extension is installed, I am able to add it to a new app, and damn it, I can SEE the files in the Data and Extension folders! I just can't open the Eko mfa, which leads me to think that maybe it's looking for an older version of the extension... Any idea if that would be at all possible, and do you have handy a couple older versions? Even if my game uses and outdated version, I'd need the old extension at least to be able to open the mfa and remove the events before I can update to the new version of the extension.

If that's any help, we originally added the extension around June (I believe), and I see a post from you in early July announcing a new version - that's what led me to this hypothesis in the first place.

Thanks a lot!

[Phi]

Hey Gabriel, I have old versions available (see here), however I am encountering a bug with MMF2 regarding MFA loading like that.
| I've posted on the forums to no avail; Yves/Francois don't appear to acknowledge it, and the bug isn't part of my extension's code, as no code in my extension is even called by MMF2. It's something MMF2-side, which declares the extension isn't installed based on some unknown check. Contact Francois with your MFA, maybe that will resolve it; I have about 3 other issues similar to it.
| In any case, make a backup copy of any MFAs and autosaves you have with DebugObject as I cannot guarantee you will be able to open them later if you attempt to open them and fail to.
| Also check out the new beta of MMF, 258.0 RC, as it may have something to do with it.
~Phi