03300: tmmjprd, tmpdoki: [debug] Crash after OK

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03300	Crash/Freeze	Critical (emulator)	Always	Jul 10, 2009, 18:31	Jul 20, 2009, 06:33

Tester	Tafoid	View Status	Public	Platform	MAME (Self-compiled)
Assigned To	aaron	Resolution	Fixed	OS	Windows 2000
Status [?]	Resolved			Driver	metro/tmmjprd.cpp
Version	0.132u4	Fixed in Version	0.133	Build	Debug
		Fixed in Git Commit		Github Pull Request #

Summary	03300: tmmjprd, tmpdoki: [debug] Crash after OK
Description	Normal build plays fine, but the debug build crashes with a segfault: Program received signal SIGSEGV, Segmentation fault. 0x00aac57e in copyline_palette16 (dst=0x1d9a2328, src=0x1aa61812, width=320, palette=0xb4f1ff8, xborderpix=1) at src/osd/windows/drawd3d.c:1895 1895 dst++ = 0xff000000 \| palette[src++];
Steps To Reproduce
Additional Information
Github Commit

Flags	Debug build specific
Regression Version	0.132u4
Affected Sets / Systems	tmmjprd, tmpdoki

Attached Files

No.04631 etabeta Developer Jul 12, 2009, 14:34	fwiw, it doesn't happen in SDLMAME... being the problem in src/osd/windows/drawd3d.c , it was expected to be win specific, but better to confirm it ;)
No.04662 aaron Developer Jul 20, 2009, 06:33	When this happens, it means you are generating entries in your bitmap that are greater than the palette size. In this case, both sprites and tiles were capable of drawing out of range.