|
-debug option not woriking
#349572 - 01/25/16 02:57 PM
|
|
|
I tried to run the MAME Debugger, but it crashes.
Here's what happens:
C:\_PARDUZ_\_APPS_\MameMess 64>mame64 sq1 -log -debug
-----------------------------------------------------
Exception at EIP=00000000025D1EE1 (debug_view_disasm::view_update()+0x0041): ACCESS VIOLATION
While attempting to read memory at 0000000000000010
-----------------------------------------------------
RAX=0000000000000000 RBX=0000000000000000 RCX=000000000AC119E0 RDX=00000000FFFFFFFF
RSI=0000000012ACD510 RDI=7FFFFFFFFFFFFFFF RBP=0000000000229E20 RSP=0000000000229DA0
R8=0000000000000320 R9=0000000000000050 R10=0000000000000014 R11=0000000000229CEC
R12=00000000121B27B0 R13=00000000120262A0 R14=00000000775536F4 R15=0000000000000000
-----------------------------------------------------
Stack crawl:
0000000000229DA0: 00000000025D1EE1 (debug_view_disasm::view_update()+0x0041)
0000000000229EA0: 00000000025CF063 (debug_view::set_source(debug_view_source const&)+0x0093)
0000000000229F00: 000000000151BCED (debugview_info::maxwidth()+0x004d)
000000000022A0B0: 000000000151A76E (consolewin_info::consolewin_info(debugger_windows_interface&)+0x025e)
000000000022A130: 00000000014FE3F0 (debugger_windows::wait_for_debugger(device_t&, bool)+0x01b0)
000000000022A160: 00000000014F73D9 (osd_common_t::wait_for_debugger(device_t&, bool)+0x0019)
000000000022A1E0: 00000000025CD749 (device_debug::instruction_hook(unsigned int)+0x0289)
000000000022A2A0: 0000000001C0C572 (m68000_base_device::execute_run()+0x0a02)
000000000022A340: 000000000257B922 (device_scheduler::timeslice()+0x0312)
000000000022A3A0: 000000000253B0F8 (running_machine::run(bool)+0x0148)
000000000022F770: 000000000253609C (machine_manager::execute()+0x01fc)
000000000022F950: 0000000002487599 (cli_frontend::execute(int, char**)+0x0839)
000000000022FDF0: 00000000014F500B (utf8_main(int, char**)+0x016b)
000000000022FE50: 000000000297311E (wmain+0x007e)
000000000022FF20: 000000000040140C (__tmainCRTStartup+0x025c)
000000000022FF50: 000000000040153B (mainCRTStartup+0x001b)
000000000022FF80: 00000000774359CD (BaseThreadInitThunk+0x000d)
000000000022FFD0: 000000007766B981 (RtlUserThreadStart+0x0021)
C:\_PARDUZ_\_APPS_\MameMess 64>
From the error.log:
[:esp] Device ':esp' did not register any state to save!
[ Clock = 29761
Soft reset
What should i look for? Am I missing some dll for the UI?
-edit-
System is a Win7-64 PRO PC, the command is launched from the CMD window with Admin rights.
The ROM works as expected without the -debug option.
(LOL for the ": pump" emoticon popping out 
Edited by Parduz (01/25/16 03:05 PM)
|
|
|
|
Re: -debug option not woriking
[Re: Parduz]
#349573 - 01/25/16 03:22 PM
|
|
|
I can confirm this crash when using the sq1 driver, it should probably be reported on Mametesters if there isn't already a report, it's a legitimate bug.
> I tried to run the MAME Debugger, but it crashes.
> Here's what happens:
>
>
> C:\_PARDUZ_\_APPS_\MameMess 64>mame64 sq1 -log -debug
>
> -----------------------------------------------------
> Exception at EIP=00000000025D1EE1 (debug_view_disasm::view_update()+0x0041): ACCESS
> VIOLATION
> While attempting to read memory at 0000000000000010
> -----------------------------------------------------
> RAX=0000000000000000 RBX=0000000000000000 RCX=000000000AC119E0 RDX=00000000FFFFFFFF
> RSI=0000000012ACD510 RDI=7FFFFFFFFFFFFFFF RBP=0000000000229E20 RSP=0000000000229DA0
> R8=0000000000000320 R9=0000000000000050 R10=0000000000000014 R11=0000000000229CEC
> R12=00000000121B27B0 R13=00000000120262A0 R14=00000000775536F4 R15=0000000000000000
> -----------------------------------------------------
> Stack crawl:
> 0000000000229DA0: 00000000025D1EE1 (debug_view_disasm::view_update()+0x0041)
> 0000000000229EA0: 00000000025CF063 (debug_view::set_source(debug_view_source
> const&)+0x0093)
> 0000000000229F00: 000000000151BCED (debugview_info::maxwidth()+0x004d)
> 000000000022A0B0: 000000000151A76E
> (consolewin_info::consolewin_info(debugger_windows_interface&)+0x025e)
> 000000000022A130: 00000000014FE3F0 (debugger_windows::wait_for_debugger(device_t&,
> bool)+0x01b0)
> 000000000022A160: 00000000014F73D9 (osd_common_t::wait_for_debugger(device_t&,
> bool)+0x0019)
> 000000000022A1E0: 00000000025CD749 (device_debug::instruction_hook(unsigned
> int)+0x0289)
> 000000000022A2A0: 0000000001C0C572 (m68000_base_device::execute_run()+0x0a02)
> 000000000022A340: 000000000257B922 (device_scheduler::timeslice()+0x0312)
> 000000000022A3A0: 000000000253B0F8 (running_machine::run(bool)+0x0148)
> 000000000022F770: 000000000253609C (machine_manager::execute()+0x01fc)
> 000000000022F950: 0000000002487599 (cli_frontend::execute(int, char**)+0x0839)
> 000000000022FDF0: 00000000014F500B (utf8_main(int, char**)+0x016b)
> 000000000022FE50: 000000000297311E (wmain+0x007e)
> 000000000022FF20: 000000000040140C (__tmainCRTStartup+0x025c)
> 000000000022FF50: 000000000040153B (mainCRTStartup+0x001b)
> 000000000022FF80: 00000000774359CD (BaseThreadInitThunk+0x000d)
> 000000000022FFD0: 000000007766B981 (RtlUserThreadStart+0x0021)
>
> C:\_PARDUZ_\_APPS_\MameMess 64>
>
>
> From the error.log:
>
> [:esp] Device ':esp' did not register any state to save!
> [ Clock = 29761
> Soft reset
>
>
> What should i look for? Am I missing some dll for the UI?
> -edit-
> System is a Win7-64 PRO PC, the command is launched from the CMD window with Admin
> rights.
> The ROM works as expected without the -debug option.
>
> (LOL for the ": pump" emoticon popping out
|
|
|
|
Re: -debug option not woriking
[Re: Haze]
#349574 - 01/25/16 04:18 PM
|
|
|
Micko has fixed this in the latest code.
|
|
|
|
Re: -debug option not woriking
[Re: Haze]
#349575 - 01/25/16 04:22 PM
|
|
|
Thanks!
> Micko has fixed this in the latest code.
Sorry if the incoming question is dumb, i'm not so fond on these kind of things..... does it means that i need to wait for a new compiled MAME (not willing to compile MAME by myself)?
Thanks again 
|
|
|
|
Re: -debug option not woriking
[Re: Parduz]
#349580 - 01/25/16 07:15 PM
|
|
|
> > Micko has fixed this in the latest code.
> Sorry if the incoming question is dumb, i'm not so fond on these kind of things.....
> does it means that i need to wait for a new compiled MAME (not willing to compile
> MAME by myself)?
Yes, you will have to rebuild MAME yourself or failing that wait for someone else to rebuild MAME for you. Micko doesn't have supernatural powers allowing him to patch MAME on your PC.
|
|
|
|
Re: -debug option not woriking
[Re: Vas Crabb]
#349581 - 01/25/16 07:23 PM
|
|
|
> > > Micko has fixed this in the latest code.
> > Sorry if the incoming question is dumb, i'm not so fond on these kind of
> things.....
> > does it means that i need to wait for a new compiled MAME (not willing to compile
> > MAME by myself)?
>
> Yes, you will have to rebuild MAME yourself or failing that wait for someone else to
> rebuild MAME for you. Micko doesn't have supernatural powers allowing him to patch
> MAME on your PC.
I did'nt meant that, your sarcasm is unnecessary.
I've seen other open source programs with daily/weekly or special builds (like some android roms), and since i don't know the whole GITHUB mechanism i was wondering if a compiled exe is "generated" from the correction or not.
|
|
|
Index 
Threaded 
-debug option not woriking
Reply
Clock = 29761
[Re: 
