04822: All sets in cdi.c: Crash after OK

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04822	Crash/Freeze	Critical (emulator)	Always	May 13, 2012, 06:47	May 17, 2012, 19:27

Tester	B2K24	View Status	Public	Platform	MAME (Self-compiled)
Assigned To	micko	Resolution	Fixed	OS	Windows Vista/7 (64-bit)
Status [?]	Resolved			Driver	philips/cdi.cpp
Version	0.145u8	Fixed in Version	0.146	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	04822: All sets in cdi.c: Crash after OK
Description	Run any set that uses the cdi.c driver and you get Crash after OK
Steps To Reproduce
Additional Information	Sorry, I haven't learned how to get a backtrace yet or else I would have pasted that information in description part.
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets in cdi.c

Attached Files

No.08561 Tafoid Administrator May 13, 2012, 09:37	Testing quizard.. the game boots up and after nearly 20 seconds, the title screen comes up which matches behavior from 0.142. No crash on 32-bit.
No.08562 Fujix Administrator May 13, 2012, 11:08	Please check the last section of http://mametesters.org/tutorial.html , which describes how to make backtraces.
No.08563 haynor666 Tester May 13, 2012, 11:33	All games don't boot correctly (it is probably expected) but no crash on 145u8 64bit.
No.08564 Fujix Administrator May 13, 2012, 12:16	I guess the reporter doesn't have necessary files..
No.08572 B2K24 Senior Tester May 13, 2012, 17:11	I have all files and even if I did not it wouldn't cause mame64.exe to close and crash out automatically. It is experiencing the same activity as already reported games in the aleck64 driver on my machine even with cfg, nvram, diff directories cleaned. Looking at the backtrace instructions now that were linked, but the instructions on that are rather vague. I'm attempting it.
No.08575 haynor666 Tester May 13, 2012, 17:53	Actually I can confirm aleck64 crashing after OK
No.08577 B2K24 Senior Tester May 13, 2012, 18:01	yes because Tafoid already filed the report and it has been resolved.
No.08582 B2K24 Senior Tester May 13, 2012, 19:59	Here is a backtrace (gdb) bt #0 0x000000000265c61a in ioport_port::machine (this=0x0) at src/emu/ioport.c:2372 #1 0x000000000265c63d in ioport_port::manager (this=0x0) at src/emu/ioport.c:2383 #2 0x000000000265c762 in ioport_port::read (this=0x0) at src/emu/ioport.c:2408 #3 0x0000000001dc5fb9 in cdislave_device::perform_mouse_update ( this=0x30dfa180) at src/mame/machine/cdislave.c:82 #4 0x0000000001dc6209 in cdislave_device::mouse_update (this=0x30dfa180, field=..., param=0x0, oldval=0, newval=2) at src/mame/machine/cdislave.c:122 #5 0x0000000003891538 in delegate_base<void, ioport_field&, void*, unsigned int , unsigned int, _noparam>::operator() (this=0x361856e8, p1=..., p2=0x0, p3=0, p4=2) at src/emu/delegate.h:620 #6 0x0000000002664819 in dynamic_field::write (this=0x3618b580, newval=2) at src/emu/ioport.c:3979 #7 0x000000000265cb85 in ioport_port::frame_update (this=0x36181b30, mouse_field=0x0) at src/emu/ioport.c:2462 #8 0x000000000265fff1 in ioport_manager::frame_update (this=0x22a7e8) at src/emu/ioport.c:3022 #9 0x000000000265fdc1 in ioport_manager::frame_update_callback ( this=0x22a7e8) at src/emu/ioport.c:2970 #10 0x0000000003891191 in delegate_base<void, _noparam, _noparam, _noparam, _nop aram, _noparam>::operator() (this=0x3611f0c8) at src/emu/delegate.h:616 #11 0x0000000002679189 in running_machine::call_notifiers (this=0x228d10, which=MACHINE_NOTIFY_FRAME) at src/emu/machine.c:721 #12 0x000000000297aae9 in video_manager::frame_update (this=0x3611b650, debug=false) at src/emu/video.c:247 #13 0x00000000025993ba in screen_device::vblank_begin (this=0x30df8cb0) at src/emu/screen.c:808 #14 0x0000000002597e7e in screen_device::device_timer (this=0x30df8cb0, timer=..., id=0, param=0, ptr=0x0) at src/emu/screen.c:393 #15 0x000000000380c5fa in device_t::timer_expired (this=0x30df8cb0, timer=..., id=0, param=0, ptr=0x0) at src/emu/device.h:223 #16 0x00000000025abdaf in device_scheduler::execute_timers (this=0x22e770) at src/emu/schedule.c:911 #17 0x00000000025aaa7d in device_scheduler::timeslice (this=0x22e770) at src/emu/schedule.c:430 #18 0x0000000002677e68 in running_machine::run (this=0x228d10, firstrun=true) at src/emu/machine.c:389 #19 0x0000000002594584 in mame_execute (options=..., osd=...) at src/emu/mame.c:189 #20 0x0000000002926315 in cli_frontend::execute (this=0x22fce0, argc=4, argv=0x30fb5720) at src/emu/clifront.c:252 #21 0x0000000001e106cf in utf8_main (argc=4, argv=0x30fb5720) at src/osd/windows/winmain.c:482 #22 0x0000000002c26e86 in wmain (argc=4, argv=0x30fb2350) at src/osd/windows/main.c:82 #23 0x000000000040142e in __tmainCRTStartup () at ../mingw-w64-crt/crt/crtexe.c:282 #24 0x0000000076fd652d in KERNEL32!BaseThreadInitThunk () from C:\Windows\system32\kernel32.dll #25 0x0000000000000000 in ?? () (gdb)
No.08597 Tafoid Administrator May 16, 2012, 16:16	This should be fixed. If you can get a daily build from current SVN and try it out for sure and let us know - that would be great.
No.08602 B2K24 Senior Tester May 17, 2012, 19:27	Thanks very much. I can confirm it being fixed now after compiling latest SVN.