Doomworld Forums > Classic Doom > Source Ports > Can WinMBF bugs be tracked?

Author All times are GMT. The time now is 05:00.

printz CRAZY DUMB ZEALOT Posts: 6849 Registered: 06-06 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. 12-26-11 12:17 # Profile || Blog || PM || Search || Add Buddy IP || Edit/Delete || Quote

wesleyjohnson Member Posts: 486 Registered: 04-09 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. 12-27-11 19:18 # Profile || Blog || PM || Search || Add Buddy IP || Edit/Delete || Quote

All times are GMT. The time now is 05:00.

Doomworld Forums > Classic Doom > Source Ports > Can WinMBF bugs be tracked? Show Printable Version | Email this Page | Subscribe to this Thread Forum Rules: You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is OFF vB code is ON Smilies are OFF [IMG] code is ON

< Contact Us - Doomworld >

Powered by: vBulletin Version 2.2.5
Copyright ©2000, 2001, Jelsoft Enterprises Limited.