This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: No useful backtrace after uncaught exception in std::thread

From: Tobias RingstrÃm <tobias at ringis dot se>
To: gcc-help at gcc dot gnu dot org
Date: Tue, 15 Nov 2011 21:46:12 +0100
Subject: Re: No useful backtrace after uncaught exception in std::thread
References: <4EC2C395.3010304@ringis.se> <201111152129.52624.pluto@agmk.net> <CAH6eHdSnDNHd4VvNcKMyAU4Dv5CAGRGBBjR8yuHsAmnbwL7d8w@mail.gmail.com> <201111152142.06503.pluto@agmk.net>

On 2011-11-15 21:42, PaweÅ Sikora wrote:

i've used gcc commandline from original post (w/o -pthread), so it looks like another bug that allows std::thread compilation w/o (-pthread) -D_REENTRANT definition.

No, that was just an operator error, or more precisely my cut'n-paste that missed the trailing part... Sorry about the confusion.

/Tobias

References:
- No useful backtrace after uncaught exception in std::thread
  - From: Tobias RingstrÃm
- Re: No useful backtrace after uncaught exception in std::thread
  - From: PaweÅ Sikora
- Re: No useful backtrace after uncaught exception in std::thread
  - From: Jonathan Wakely
- Re: No useful backtrace after uncaught exception in std::thread
  - From: PaweÅ Sikora

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]