|Summary:||[abrt] mame: std::__replacement_assert(): mame killed by SIGABRT|
|Product:||[Fedora] Fedora||Reporter:||Aleš Zima <ales.zima>|
|Component:||mame||Assignee:||Julian Sikorski <belegdol>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||mame-0.232-2.fc33||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2021-06-23 01:13:37 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Aleš Zima 2021-06-11 07:30:32 UTC
Comment 1 Aleš Zima 2021-06-11 07:30:36 UTC
Created attachment 1790113 [details] File: backtrace
Comment 2 Aleš Zima 2021-06-11 07:30:38 UTC
Created attachment 1790114 [details] File: core_backtrace
Comment 3 Aleš Zima 2021-06-11 07:30:40 UTC
Created attachment 1790115 [details] File: cpuinfo
Comment 4 Aleš Zima 2021-06-11 07:30:42 UTC
Created attachment 1790116 [details] File: environ
Comment 5 Aleš Zima 2021-06-11 07:30:43 UTC
Created attachment 1790117 [details] File: limits
Comment 6 Aleš Zima 2021-06-11 07:30:45 UTC
Created attachment 1790118 [details] File: maps
Comment 7 Aleš Zima 2021-06-11 07:30:47 UTC
Created attachment 1790119 [details] File: mountinfo
Comment 8 Aleš Zima 2021-06-11 07:30:48 UTC
Created attachment 1790120 [details] File: open_fds
Comment 9 Aleš Zima 2021-06-11 07:30:49 UTC
Created attachment 1790121 [details] File: proc_pid_status
Comment 10 Julian Sikorski 2021-06-12 07:07:00 UTC
I unfortunately cannot reproduce this. mame-0.232 is working on two of my machines, an nvidia desktop and an amd laptop. Could you elaborate a bit more how you are making the assertion happen? Are you starting mame without a rom name and then picking one from the list? Or starting the machine directly (e.g. mame pacman)? There used to be an assertion when trying to display mameinfo.dat which is going to be fixed in 0.233.
Comment 11 Aleš Zima 2021-06-12 09:57:17 UTC
@Julian I have two desktops - AMD R7 with Radeon graphics and AMD R7 with nVidia graphics. Both running Fedora 34. And both have exactly same issue with mame (mame-0.232-1.fc34.x86_64). I use mame for running emulations of old dedicated chess computers. For example Saitek RISC2500: [ales@workstation ~]$ mame risc2500 /usr/include/c++/11/string_view:234: constexpr const value_type& std::basic_string_view<_CharT, _Traits>::operator(std::basic_string_view<_CharT, _Traits>::size_type) const [with _CharT = char; _Traits = std::char_traits<char>; std::basic_string_view<_CharT, _Traits>::const_reference = const char&; std::basic_string_view<_CharT, _Traits>::size_type = long unsigned int]: Assertion '__pos < this->_M_len' failed. Aborted (core dumped) [ales@workstation ~]$ When compile and run mame from GitHub (MAME v0.232 (mame0232-168-g76c34a79b90)) everything is fine.
Comment 12 Aleš Zima 2021-06-12 09:57:58 UTC
@Julian Now i've tested on 3rd computer - laptop with intel Core i7 and Fedora 34. Exactly same result!!! It's hard to believe, that this can't be reproduced.
Comment 13 Julian Sikorski 2021-06-13 07:57:18 UTC
I can reproduce it with a2500, thanks. Fedora mame package uses the standard Fedora compiler flags which includes -Wp,-D_GLIBCXX_ASSERTIONS. I have already found two cases in which this causes assertions to trigger. Was it working with 0.231? If so, one of us needs to bisect and report a bug upstream.
Comment 14 Julian Sikorski 2021-06-13 09:05:05 UTC
The assertions go back as far as 0.228-2.fc34. Looks like bisecting is not going to be that trivial.
Comment 15 Julian Sikorski 2021-06-13 10:15:14 UTC
I have managed to find a working revision. I still have some steps to bisect but it appears that the assertion might be related to switch from .png to .svg chess pieces.
Comment 16 Aleš Zima 2021-06-13 10:23:43 UTC
I would like to help, but I'm just a slightly advanced user.
Comment 17 Fedora Update System 2021-06-14 06:01:58 UTC
FEDORA-2021-8793f80b80 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8793f80b80
Comment 18 Fedora Update System 2021-06-14 06:02:41 UTC
FEDORA-2021-caa880a8ae has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-caa880a8ae
Comment 19 Fedora Update System 2021-06-15 01:08:23 UTC
FEDORA-2021-caa880a8ae has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-caa880a8ae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-caa880a8ae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 20 Fedora Update System 2021-06-15 01:53:41 UTC
FEDORA-2021-8793f80b80 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8793f80b80` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8793f80b80 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 21 Fedora Update System 2021-06-23 01:07:03 UTC
FEDORA-2021-caa880a8ae has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Comment 22 Fedora Update System 2021-06-23 01:13:37 UTC
FEDORA-2021-8793f80b80 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.