Re: [RFC][Patch] Fix gdb failure to access tls data for parent thread

[Daniel Jacobowitz <drow@false.org>]

On Thu, Feb 12, 2009 at 11:13:26AM +0530, Vinay Sridhar wrote:
> On Wed, 2009-02-11 at 10:53 -0500, Daniel Jacobowitz wrote:
> > On Wed, Feb 11, 2009 at 02:01:08PM +0530, Vinay Sridhar wrote:
> > > Daniel,
> > > 
> > > Sorry for the late response. I can confirm that attach_thread is not
> > > called on the parent thread. The test case I had listed in my earlier
> > > mail uses OMP for thread creation. Could that have something to do with
> > > this?
> > 
> > Well, it shouldn't; libgomp uses the normal POSIX thread interfaces.
> > I assume you're using GCC -fopenmp, right?  Or is this another OpenMP
> > implementation?
> > 
> 
> I used IBM's XLC compiler which has an inbuilt OpenMP implementation.

Sorry for the delay, I missed your message.

In that case, you need to determine whether it is using POSIX threads
or whether it is using clone directly and ignoring the thread library.
If it is not using the POSIX threads library, how is it handling TLS
inside the threads?  If it is using pthread_create, why didn't we get
a notification about it?

-- 
Daniel Jacobowitz
CodeSourcery