|
Joined: Sep 2001
Posts: 535
Senior Member
|
Senior Member
Joined: Sep 2001
Posts: 535 |
This is the command-line it will use on my system with a default MESS compile:
gcc -DCRLF=3 -DINLINE="static inline" -DLSB_FIRST -DNDEBUG
-DX64_WINDOWS_ABI -DUNICODE -D_UNICODE -Dmain=utf8_main
-DMESS -DWINVER=0x0400 -D_WIN32_IE=0x0501 -DDECL_SPEC=
-DZEXTERN=extern -DNATIVE_DRC=drcbe_x86_be_interface -pipe
-O3 -Werror -fno-strict-aliasing -Wall -Wcast-align -Wundef
-Wformat-security -Wwrite-strings -Wno-sign-compare -Isrc/mess
-Iobj/windows/mess/mess/layout -Isrc/emu -Iobj/windows
/mess/emu -Iobj/windows/mess/emu/layout -Isrc/lib/util
-Isrc/osd -Isrc/osd/windows -Isrc/lib/expat -Isrc/lib/zlib
-include src/osd/windows/winprefix.h
-DDIRECTINPUT_VERSION=0x0700 -x c++ -std=gnu++98 -Isrc/mame
-Isrc/mess/osd -Isrc/mess/osd/windows -Isrc/mess/tools
-Isrc/mess/tools/imgtool -Isrc/mess/tools/castool -Isrc/osd
/winui -Isrc/mess/osd/winui -c src/mame/drivers/megadriv.c -o
obj/windows/mess/mame/drivers/megadriv.o
I wasn't able to reproduce the crash though. Maybe there was some change, that made this crash disappear. I checked the SVN history and it was changed in the 0.137u2 and 0.137u3 update. I already tried reverting to u3, but I still wasn't able to experience the crash. If you can reproduce the crash please change the -DINLINE bit to "-DINLINE=inline" see, if it still crashes and then put "gdb --args" in front the command-line and run it with "r". If you get the crash in gdb, please type "bt full" to get a (hopefully not totally useless) backtrace, that can be submitted to the mingw64 team.
|
|
|
|
Joined: Mar 2001
Posts: 16,960 Likes: 76
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 16,960 Likes: 76 |
Hap rearranged the megadriv code in 0.138 to work around the XP crash, so if it does still happen that would be interesting.
|
|
|
|
Joined: Sep 2001
Posts: 535
Senior Member
|
Senior Member
Joined: Sep 2001
Posts: 535 |
Argh...that's too bad. I didn't recognize any changes in 0.138. Neither do I see any changes in 0.138, that are done to the megadriv code. Could you give me a pointer?
And do you know, that I hate workarounds for such things?
|
|
|
|
Joined: Mar 2001
Posts: 16,960 Likes: 76
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 16,960 Likes: 76 |
Literally it was just changing the order of a few lines in one of the functions.
|
|
|
|
Joined: Sep 2001
Posts: 535
Senior Member
|
Senior Member
Joined: Sep 2001
Posts: 535 |
Are you really sure the code made it? The only changes to megadriv.c in the 0.138 cycle were additional inputs for the bootlegs and an unused variable change from me.
|
|
|
|
Joined: Mar 2001
Posts: 16,960 Likes: 76
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 16,960 Likes: 76 |
It's definitely in current (MAME) SVN, and I'm fairly sure it was before the 0.138 cutoff but I deleted the relevant emails already.
|
|
|
|
Joined: Mar 2006
Posts: 1,074 Likes: 5
Very Senior Member
|
Very Senior Member
Joined: Mar 2006
Posts: 1,074 Likes: 5 |
Modified: trunk/src/mame/drivers/megadriv.c
===================================================================
--- trunk/src/mame/drivers/megadriv.c 2010-05-16 14:04:49 UTC
+++ trunk/src/mame/drivers/megadriv.c 2010-05-16 16:51:31 UTC
@@ -6576,19 +6576,17 @@
DRIVER_INIT( _32x )
{
-
-
_32x_dram0 = auto_alloc_array(machine, UINT16, 0x40000/2);
_32x_dram1 = auto_alloc_array(machine, UINT16, 0x40000/2);
memset(_32x_dram0, 0x00, 0x40000);
memset(_32x_dram1, 0x00, 0x40000);
- _32x_palette = auto_alloc_array(machine, UINT16, 0x200/2);
_32x_palette_lookup = auto_alloc_array(machine, UINT16, 0x200/2);
+ _32x_palette = auto_alloc_array(machine, UINT16, 0x200/2);
- memset(_32x_palette, 0x00, 0x200);
memset(_32x_palette_lookup, 0x00, 0x200);
+ memset(_32x_palette, 0x00, 0x200);
_32x_display_dram = _32x_dram0;
^ that patch, by hap, was to work around the compiler error. LN
"When life gives you zombies... *CHA-CHIK!* ...you make zombie-ade!"
|
|
|
|
Joined: Sep 2001
Posts: 535
Senior Member
|
Senior Member
Joined: Sep 2001
Posts: 535 |
This change is *not* in the released 0.138 source and the crash is gone for most of the people without the changes.
|
|
|
|
Joined: Sep 2001
Posts: 535
Senior Member
|
Senior Member
Joined: Sep 2001
Posts: 535 |
The change is in 0.138u1 and it apparently causes the error to appear for people, that never saw it.
|
|
|
|
Joined: Mar 2001
Posts: 16,960 Likes: 76
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 16,960 Likes: 76 |
Yeah, he's seeing an entirely different version of the crash apparently - I think he may genuinely have bad RAM based on some of his commmits to "avoid" it since u1.
|
|
|
Forums9
Topics9,158
Posts119,916
Members5,034
|
Most Online1,283 Dec 21st, 2022
|
|
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!
|
|
|
|