This is the mail archive of the
mailing list for the libstdc++ project.
Re: Thread safety clarification
[Get raw message]
- To: David Waite <mass at akuma dot org>
- Subject: Re: Thread safety clarification
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 13 Nov 2001 09:48:18 -0800 (PST)
- Cc: libstdc++ at gcc dot gnu dot org
> I will do some more experimentation tonight to find out which concrete
> option(s) cause problems.
> My current problem looks like a race condition in v3, nine times out of
> ten it has reported a problem related to strings, and I've seen memory
> debugging tools like dmalloc writing over the data in constant global
> strings (marking it off as deleted).
> Yep, it was more of a 'can someone tell me where to start' than a 'can
> someone tell me what the problem is' - I'll grab more specifics tonight.
> Will do. Is there anything special I need to do to get debugging symbols
> for optimized builds?
When building the library, you can pass in CXXFLAGS arguments.
make CXXFLAGS='-g -O0' all
Once you find the -fxxx flag that causes the error, just pass it in here.
> I'm trying to
> get something substantially smaller than 10k lines of code to illustrate
> the problem, though. :-)