This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 0/6] Demangle minimal symbol names in worker threads
- From: Tom Tromey <tom at tromey dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Tom Tromey <tom at tromey dot com>, gdb-patches at sourceware dot org
- Date: Mon, 11 Mar 2019 16:39:15 -0600
- Subject: Re: [RFC 0/6] Demangle minimal symbol names in worker threads
- References: <20190309172300.2764-1-tom@tromey.com> <83tvgb7we9.fsf@gnu.org>
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> Thanks, but is std::thread portable enough? E.g., I recall problems
Eli> with it in MinGW.
I asked around and learned that std::thread should work fine if you have
winpthreads, which apparently is used by default for mingw-w64.
I don't actually know much about the mingw world, so I don't know if
that is good enough or not. Could you say?
Jonathan Wakely also once wrote a port of libstdc++ to the Win32 API,
but couldn't find help with testing, so never checked it in.
Eli> Same question regarding delivering signals to threads.
If the signal thing is broken in this series, then it is probably
already broken today. However I think it ought to be ok as SEGV is a
synchronous signal; that is, it is delivered to the faulting thread.
Does that address your concern here?
Tom