_gthread_init crash

_gthread_init crash

[Michael]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

I have compiled my app using musl entirely statically however when it is
run on initialization it crashes with the attached stacktrace under
x86_64.  Is this because the local stuff in musl is not fully finished?

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000000006ccecf in __gthread_once ()
#2  0x00000000006cd285 in std::locale::_S_initialize() ()
#3  0x00000000006cd012 in std::locale::locale() ()
#4  0x0000000000683614 in std::basic_streambuf<char, std::char_traits<char>
>::basic_streambuf() ()
#5  0x00000000006ae590 in __gnu_cxx::stdio_sync_filebuf<char,
std::char_traits<char> >::stdio_sync_filebuf(_IO_FILE*) ()
#6  0x0000000000684beb in std::ios_base::Init::Init() ()
#7  0x00000000004021ee in
_GLOBAL__sub_I__ZN9wxPrivate18GetUntypedNullDataEv ()
#8  0x00000000006f5056 in __do_global_ctors_aux ()
#9  0x000000000040012b in _init ()
#10 0x0000000000000000 in ?? ()

[-- Attachment #2: Type: text/html, Size: 1202 bytes --]

Re: _gthread_init crash

[Jens Gustedt]

[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]

Hi,

Am Dienstag, den 14.10.2014, 17:07 +1100 schrieb Michael:
> I have compiled my app using musl entirely statically however when it
> is run on initialization it crashes with the attached stacktrace under
> x86_64.  Is this because the local stuff in musl is not fully
> finished?
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x00000000006ccecf in __gthread_once ()
> #2  0x00000000006cd285 in std::locale::_S_initialize() ()
> #3  0x00000000006cd012 in std::locale::locale() ()
> #4  0x0000000000683614 in std::basic_streambuf<char,
> std::char_traits<char> >::basic_streambuf() ()
> #5  0x00000000006ae590 in __gnu_cxx::stdio_sync_filebuf<char,
> std::char_traits<char> >::stdio_sync_filebuf(_IO_FILE*) ()
> #6  0x0000000000684beb in std::ios_base::Init::Init() ()
> #7  0x00000000004021ee in
> _GLOBAL__sub_I__ZN9wxPrivate18GetUntypedNullDataEv ()
> #8  0x00000000006f5056 in __do_global_ctors_aux ()
> #9  0x000000000040012b in _init ()
> #10 0x0000000000000000 in ?? ()

This looks as if you are using the native C++ lib, and this is using
internal stuff from glibc under the hood. In particular, here it seems
to be using glibc's implementation of pthread_once to initialize things.

Not surprising that this doesn't work.

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]