Sign in to follow this  
Followers 0

Can WinMBF bugs be tracked?

I'm having some problems (in a mod) that cause the game to crash in WinMBF, but work fine in Eternity. All that WinMBF tells me is the "SDL Parachute Deployed" procedure. Is it possible to make it display the source of the error so I can report the bugs properly?

It's a WAD/BEX combo mod.

Share this post


Link to post

I believe the SDL parachute is an optional piece of code to catch exceptions. I have come across the term and one doom port disables it to get a core dump instead, but I have been ground down trying to get DoomLegacy to compile and run on a Mac OSX, and may be confused a little.
In the belief that such things are many times wad fields that are accepted or fixed by one port, but crash another, you could get a copy of the latest SVN of DoomLegacy and run it with the -v2 switch (verbose level 2), which will get a couple pages of wad incontistency warnings.
Or the -devparm switch on many ports.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0