 No.21172
cuavas Administrator
Mar 17, 2023, 08:02
|
That stack trace is impossible. Your symbols don't match your executable. The stack trace in the issue you linked to is impossible, too. In fact, I'd say the main way the issues are similar is that they both have impossible stack traces. |
|---|---|
|
No.21173
cuavas Administrator
Mar 17, 2023, 14:52
|
Actual stack trace from a recent build (note that you may have to play for a while before it crashes, it doesn’t crash on starting the game): #0 0x00007ff73eb6a600 in handler_entry_read_memory_bank<0, 0>::read(unsigned int, unsigned char) const () #1 0x00007ff73a2cb03d in z80_device::rm(unsigned short) () #2 0x00007ff73a2ee3b4 in z80_device::op_dd() () #3 0x00007ff73a2cebe4 in z80_device::execute_run() () #4 0x00007ff739e05a23 in device_scheduler::timeslice() () #5 0x00007ff739e01d78 in running_machine::run(bool) () #6 0x00007ff73d9b9b8b in mame_machine_manager::execute() () #7 0x00007ff741076b2f in cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) () #8 0x00007ff74107713d in cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) () #9 0x00007ff73d9b47a9 in emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) () #10 0x00007ff7423d8cc9 in main () |
|
No.21174
cuavas Administrator
Mar 17, 2023, 15:06
|
I may as well try to untangle some of the mess of dependencies between machine configurations. It’s pretty clear too many things are pulling in the wrong bases. |
 No.21175
Hirudov Tester
Mar 17, 2023, 17:37
|
Here is a video of my MAME crashing I don't know abut the symbols. I am using the official Windows64 version from https://www.mamedev.org I also used the XP 32 bit version (unofficial, unsupported) with same result- crash. Shall I use a debug version for reporting bugs? |
|
No.21176
cuavas Administrator
Mar 17, 2023, 18:23
|
Your symbols don’t match your executable if you’re getting completely bogus stack traces like that. A debug build just enables assertions. |
 No.21177
Tafoid Administrator
Mar 17, 2023, 18:52
|
Did some checking on this.. a 0.226 to 0.227 regression Specifically, November 2 to November 3, 2020 in my daily build testing. I checked my test notes for that day and this machine was not selected for testing because there were no drivers or devices which affected this. Checking the emulator core files, however, this is the big day of EMUMEM changes: https://github.com/mamedev/mame/commit/b8c338858a101d14308c64c87b0f714db4f05326 This is the likely regression point. |