03021: afire, spfghmk2, spfghmk22: Access Violation

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03021	Crash/Freeze	Critical (emulator)	Random	Mar 12, 2009, 21:27	Feb 25, 2010, 21:27

Tester	Firewave	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Unable to reproduce	OS
Status [?]	Closed			Driver	dataeast/astrof.cpp
Version	0.130	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	03021: afire, spfghmk2, spfghmk22: Access Violation
Description	----------------------------------------------------- Exception at EIP=004BE195: ACCESS VIOLATION While attempting to read memory at 0023001C ----------------------------------------------------- EAX=000000E1 EBX=0502C4E0 ECX=0000BA60 EDX=000000E0 ESI=000000F6 EDI=0040124B EBP=0022FCE8 ESP=0022FC70
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version	0.130
Affected Sets / Systems	afire, spfghmk2, spfghmk22

Attached Files

No.03954 Tafoid Administrator Mar 12, 2009, 21:46	Tried 0.130 and my symbols+debug build on each - no repro in my attempts.
No.04471 Firewave Senior Tester Jun 9, 2009, 15:12	With the official 0.132 binary I get unreproducible crashes in afire, spfgmk22 and tomahaw1.
No.04713 Firewave Senior Tester Jul 26, 2009, 23:36 edited on: Jul 26, 2009, 23:44	With the official debug binary of 0.133 I had crashes in all of the acombat.c games. I am not able to reproduce those outside of mame_regtest. Still investigating. Here the message from abattle: ----------------------------------------------------- Exception at EIP=004C8BE5: ACCESS VIOLATION While attempting to read memory at 00230008 ----------------------------------------------------- EAX=000000F3 EBX=12B11000 ECX=12B11000 EDX=000000F3 ESI=00FF0000 EDI=00000010 EBP=0022FC88 ESP=0022FC10 The memory it tries to read is similar in all sets. It's always in the 002300xx range.
No.04716 Firewave Senior Tester Jul 27, 2009, 00:03	I am able to reproduce the crash with the official 0.133 debug binary now. I have to run it in gdb: gdb --args mamed -window astrof Unfortunately the build doesn't have any symbols, so I just get this from gdb: Program received signal SIGSEGV, Segmentation fault. 0x004c8be5 in ?? () (gdb) bt #0 0x004c8be5 in ?? () #1 0x09231efc in ?? () #2 0x0168f901 in ?? () #3 0x00000000 in ?? ()
No.04817 R. Belmont Developer Aug 16, 2009, 00:19	Please build with symbols so you get a useful backtrace.
No.05384 Firewave Senior Tester Jan 4, 2010, 07:17 edited on: Jan 4, 2010, 07:18	In the official 0.136 binary I am getting crashes with abattle and abattle2. And they are reproducible. Here's the crash information: ----------------------------------------------------- Exception at EIP=004E9188: ACCESS VIOLATION While attempting to read memory at 00230024 ----------------------------------------------------- EAX=000000E3 EBX=0ACA6FD0 ECX=00014040 EDX=000000E2 ESI=00000000 EDI=00000006 EBP=0022FCE8 ESP=0022FC60
No.05766 Tafoid Administrator Feb 25, 2010, 21:27	Unable to confirm 32-bit or 64-bit. If it's a certain trigger that is causing it we'll reopen. Closing.