From: Michael <msbroadf@gmail.com>
To: musl@lists.openwall.com
Subject: Re: gthread_once
Date: Fri, 17 Oct 2014 21:36:56 +1100 [thread overview]
Message-ID: <CALdjXpDpWai8cuC28UyVe8dLjGS8J5WHyp8wjaNQvUmnctsGgA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
I'm not linking to glibc. gthread is a thin wrapper over pthread used by
gcc (i.e
https://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_concurrency_impl.html).
It seems my problem is related to this:
http://www.riscos.info/pipermail/gcc/2008-July/004525.html
I have compiled g++ toolchain using musl-1.1.5
Is this a bug in musl or do i need to turn off the _GTHREAD in the
libstdc++ library?
------------------------------------------------------------------
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
[-- Attachment #2: Type: text/html, Size: 2305 bytes --]
next reply other threads:[~2014-10-17 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 10:36 Michael [this message]
2014-10-17 11:42 ` gthread_once Jens Gustedt
2014-10-17 12:10 ` Rich Felker
2014-10-18 2:16 gthread_once Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALdjXpDpWai8cuC28UyVe8dLjGS8J5WHyp8wjaNQvUmnctsGgA@mail.gmail.com \
--to=msbroadf@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).