You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0.266 (mame0261-2041-g7eb725763ec), single driver build
System information
MacOS 14.5 M1 Pro.
MAME used is a single driver build using SOURCES=src/mame/msx/,src/mame/nintendo/gb.cpp
INI configuration details
No response
Emulated system/software
megaduck, hx10
Incorrect behaviour
Open MAME with debugger active (-debug -window megaduck), place cursor above the debugger above and (very) quickly scroll down (swiping with 2 fingers on the touchpad) towards/past the end of the debugger log, then the application will crash with message: "libc++abi: terminating due to uncaught exception of type std::length_error: vector"
If I scroll down slowly or normally then no crash occurs only when attempting to scroll quickly.
It does not happen when scrolling up (towards/past the start of the debugger log), nor does it happen in our debugger views as far ass I could see.
The crash happens with multiple drivers, so I assume it is a generic issue.
I do not know if a similar crash can happen on other OSes.
Backtrace from lldb:
libc++abi: terminating due to uncaught exception of type std::length_error: vector
Process 66712 stopped
MAME version
0.266 (mame0261-2041-g7eb725763ec), single driver build
System information
MacOS 14.5 M1 Pro.
MAME used is a single driver build using SOURCES=src/mame/msx/,src/mame/nintendo/gb.cpp
INI configuration details
No response
Emulated system/software
megaduck, hx10
Incorrect behaviour
Open MAME with debugger active (-debug -window megaduck), place cursor above the debugger above and (very) quickly scroll down (swiping with 2 fingers on the touchpad) towards/past the end of the debugger log, then the application will crash with message: "libc++abi: terminating due to uncaught exception of type std::length_error: vector"
If I scroll down slowly or normally then no crash occurs only when attempting to scroll quickly.
It does not happen when scrolling up (towards/past the start of the debugger log), nor does it happen in our debugger views as far ass I could see.
The crash happens with multiple drivers, so I assume it is a generic issue.
I do not know if a similar crash can happen on other OSes.
Backtrace from lldb:
libc++abi: terminating due to uncaught exception of type std::length_error: vector
Process 66712 stopped
frame #0: 0x000000019a866a60 libsystem_kernel.dylib
__pthread_kill + 8 libsystem_kernel.dylib
:-> 0x19a866a60 <+8>: b.lo 0x19a866a80 ; <+40>
0x19a866a64 <+12>: pacibsp
0x19a866a68 <+16>: stp x29, x30, [sp, #-0x10]!
0x19a866a6c <+20>: mov x29, sp
Target 0: (msxd) stopped.
(lldb) bt
__pthread_kill + 8 frame #1: 0x000000019a89ec20 libsystem_pthread.dylib
pthread_kill + 288frame Update x68k.c #2: 0x000000019a7aba30 libsystem_c.dylib
abort + 180 frame #3: 0x000000019a855d08 libc++abi.dylib
abort_message + 132frame Update h8_adc.c #4: 0x000000019a845fa4 libc++abi.dylib
demangling_terminate_handler() + 320 frame #5: 0x000000019a4e41e0 libobjc.A.dylib
_objc_terminate() + 160frame Ignore Thumbs.db (nw) #6: 0x000000019a8550cc libc++abi.dylib
std::__terminate(void (*)()) + 16 frame #7: 0x000000019a855070 libc++abi.dylib
std::terminate() + 108frame Support for the BEXT instruction #8: 0x000000019a4fe2ec libobjc.A.dylib
objc_terminate + 16 frame #9: 0x000000019a6ee3fc libdispatch.dylib
_dispatch_client_callout + 40frame Fix frequency for X1-010 and add a note. #10: 0x000000019a6f18ec libdispatch.dylib
_dispatch_continuation_pop + 600 frame #11: 0x000000019a7057f0 libdispatch.dylib
_dispatch_source_latch_and_call + 420frame ec1841: change keyboard xtal freq, add speech synthesis swre #12: 0x000000019a7043b4 libdispatch.dylib
_dispatch_source_invoke + 832 frame #13: 0x000000019a6fcac8 libdispatch.dylib
_dispatch_main_queue_drain + 748frame mc1502: restore fdc support for newer hw revisions with bios 5.3x #14: 0x000000019a6fc7cc libdispatch.dylib
_dispatch_main_queue_callback_4CF + 44 frame #15: 0x000000019a9bfad4 CoreFoundation
CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16frame MDA clone has downloadable fonts and both CGA clones have unique chargens. #16: 0x000000019a97d258 CoreFoundation
__CFRunLoopRun + 1996 frame #17: 0x000000019a97c434 CoreFoundation
CFRunLoopRunSpecific + 608frame isa_hdc: implement WRITESBUFF command #18: 0x00000001a512019c HIToolbox
RunCurrentEventLoopInMode + 292 frame #19: 0x00000001a511ffd8 HIToolbox
ReceiveNextEventCommon + 648frame isa_hdc: ec1841 compatibility #20: 0x00000001a511fd30 HIToolbox
_BlockUntilNextEventMatchingListInModeWithFilter + 76 frame #21: 0x000000019e1dbd68 AppKit
_DPSNextEvent + 660frame ti85: use direct update handler to remove boot memory mapping hacks #22: 0x000000019e9d1808 AppKit
-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 frame #23: 0x0000000102115a28 msxd
debugger_osx::wait_for_debugger(this=, device=, firststop=) at debugosx.mm:163:16 [opt]frame Convert to UTF-8. #24: 0x0000000102115ab4 msxd
non-virtual thunk to debugger_osx::wait_for_debugger(device_t&, bool) at debugosx.mm:0 [opt] frame #25: 0x000000010213e958 msxd
osd_common_t::wait_for_debugger(this=, device=, firststop=) at osdobj_common.cpp:498:14 [opt]frame Man pages (*nix): Fixed some typos and bumped version to 0.155 #26: 0x0000000100e874d0 msxd
device_debug::instruction_hook(this=0x0000000137017800, curpc=<unavailable>) at debugcpu.cpp:923:19 [opt] frame #27: 0x0000000100a6bd78 msxd
lr35902_cpu_device::execute_run() [inlined] device_execute_interface::debugger_instruction_hook(this=0x0000000135042600, curpc=) at diexec.h:231:22 [opt]frame SEGA YBoard: Mapping the port bits used to provide motor movement feedback #28: 0x0000000100a6bd70 msxd
lr35902_cpu_device::execute_run(this=0x0000000135042600) at lr35902.cpp:360:5 [opt] frame #29: 0x0000000100a717d8 msxd
non-virtual thunk to lr35902_cpu_device::execute_run() at lr35902.cpp:0 [opt]frame naomi.c: #30: 0x00000001020b094c msxd
device_scheduler::timeslice() [inlined] device_execute_interface::run(this=0x0000000135042600) at diexec.h:190:15 [opt] frame #31: 0x00000001020b093c msxd
device_scheduler::timeslice(this=0x000000016fdfe8a0) at schedule.cpp:460:14 [opt]frame naomi.c: vonot maskrom label corrected #32: 0x00000001020441b8 msxd
running_machine::run(this=0x000000016fdf9720, quiet=<unavailable>) at machine.cpp:333:17 [opt] frame #33: 0x00000001007a44a8 msxd
mame_machine_manager::execute(this=0x0000600001c54800) at mame.cpp:288:19 [opt]frame dvk_ksm: DEC VT52-compatible video terminal #34: 0x000000010007decc msxd
cli_frontend::start_execution(this=0x000000016fdfee98, manager=0x0000600001c54800, args=size=4) at clifront.cpp:277:22 [opt] frame #35: 0x000000010007f368 msxd
cli_frontend::execute(this=0x000000016fdfee98, args=) at clifront.cpp:293:3 [opt]frame mc1502: re-add speaker output, add more BIOS versions #36: 0x00000001007a56a8 msxd
emulator_info::start_frontend(options=<unavailable>, osd=<unavailable>, args=<unavailable>) at mame.cpp:453:18 [opt] frame #37: 0x00000001021b8e6c msxd
main(argc=, argv=) at sdlmain.cpp:100:9 [opt]frame Fixes for two software lists #38: 0x000000019a5160e0 dyld`start + 2360
Expected behaviour
No more crashes.
Steps to reproduce
Start MAME with debugger active, attempt to scroll fast past the end of the log in the debugger console.
Additional details
-debug -window megaduck or -debug -window hx10
The text was updated successfully, but these errors were encountered: