"_M_construct null not valid" upon bootup, started after a year of no issues.
-
@mitu I have recently built binaries for all experimental packages. I didn't mention it here sorry. I think I mentioned it on twitter. I did this due to long compile times for MAME etc.
Not sure why ES Dev binary is broken. Will check.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@BuZz said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
Not sure why ES Dev binary is broken. Will check.
Looks like an ABI mis-match. Well, that means
lr-messis installable from binary :). -
@mitu if there's is an abi mismatch it may affect that too.. I crosscompiled so I'll check/fix/rebuild everything. Sorry about this.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@BuZz It might be something else, I'll try to run through a debugger to see where it stops.
-
@mitu thanks.
-
It's crashing when trying to allocate a string, somewhere in the standard C++ lib
... #6 0x76a2a4d4 in std::__throw_logic_error(char const*) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 No symbol table info available. #7 0x0006b1f8 in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) [clone .isra.43] () No symbol table info available. #8 0x0006b2b0 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) [clone .isra.40] () No symbol table info available. #9 0x00060e48 in main ()I don't see an updates in Raspbian since the build date (27.05) that could affect the standard libraries, only some ffmpeg libs.
-
Maybe my libraries are mismatched on my cross compiler since other recent updates. Will check over the weekend.
-
I rebuilt it and I think it's ok now. Not sure what happened. Please can someone test ?
As @mitu said though, the stable version was recently updated so probably not a great need for the Dev version.
-
I'm kind of hesitant to check the binary again, but what I did to fix that was:
- run retropie manager (always enable that! :D) from a windows browser
- disable booting to emu station in configuration
- reboot the pi to prompt - it did not hang
- uninstall es dev, reinstall regular binary
That fixed it. I also tried es-dev from the source, and the pi is running correctly with it.
(By the way, I noticed that there are now so many binaries available in the experimental section that perhaps its menu could use the addition of the "update from binary" option, like the other menus do!)
-
@BazzCatt good spot with the update from binary option. I'll add it.
-
This post is deleted! -
@BazzCatt said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
I'm kind of hesitant to check the binary again, but what I did to fix that was:
- run retropie manager (always enable that! :D) from a windows browser
- disable booting to emu station in configuration
- reboot the pi to prompt - it did not hang
- uninstall es dev, reinstall regular binary
That fixed it. I also tried es-dev from the source, and the pi is running correctly with it.
(By the way, I noticed that there are now so many binaries available in the experimental section that perhaps its menu could use the addition of the "update from binary" option, like the other menus do!)
I'm getting this problem too and this is the only thread I can find on it : /
Any chance someone could translate this fix in to layman's for a newbie?
-
@WhackAMole said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
Any chance someone could translate this fix in to layman's for a newbie?
The only applicable advice in the above topic is
uninstall es dev, reinstall regular binary
Try re-installing your EmulationStation package, either from binary or from source.
-
@mitu said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
@WhackAMole said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
Any chance someone could translate this fix in to layman's for a newbie?
The only applicable advice in the above topic is
uninstall es dev, reinstall regular binary
Try re-installing your EmulationStation package, either from binary or from source.
So,, I tried the advice here from both Binary and source. I even removed all exp packages just to ensure it wasn't anything in there. The error still appears and now i've decided to attempt a complete rebuild from Raspbian up. I am also increasing SD capacity from 16gb to 32 GB to ensure space isn't an issue.
-
@goferffxi said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
@mitu said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
@WhackAMole said in "_M_construct null not valid" upon bootup, started after a year of no issues.:
Any chance someone could translate this fix in to layman's for a newbie?
The only applicable advice in the above topic is
uninstall es dev, reinstall regular binary
Try re-installing your EmulationStation package, either from binary or from source.
So,, I tried the advice here from both Binary and source. I even removed all exp packages just to ensure it wasn't anything in there. The error still appears and now i've decided to attempt a complete rebuild from Raspbian up. I am also increasing SD capacity from 16gb to 32 GB to ensure space isn't an issue.
So, I did a basic install and then removed all main packages then proceeded to reinstall the main packages from source. See what happens there
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.