Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "John Bates" <johnnybates@gmail.com>
To: gdb@sourceware.org
Subject: Re: thread local storage (__thread) variables aren't working in gdb 6.5/6.6?
Date: Tue, 19 Jun 2007 20:56:00 -0000	[thread overview]
Message-ID: <a4c7fade0706191356j2b2a93cev45ea2795d52c5a64@mail.gmail.com> (raw)
In-Reply-To: <20070619202834.GA29881@caradoc.them.org>

On 6/19/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Jun 19, 2007 at 01:22:04PM -0700, John Bates wrote:
> > I can't find any confirmation of support or non-support of thread
> > local storage on the web or in the gdb documentation. I already tried
> > 6.6 and it was the same problem. The test below seems to confirm
> > non-support on my fedora core 6 (kernel 2.6.18) x86 distribution with
> > gdb 6.5. Please let me know if I am doing something wrong for
> > debugging __thread global variables.
>
> So far, they are only supported if you are linked to libpthread.  Jan
> K. was working on this earlier.

I tried linking the program with -lpthread, if that's what you meant,
and the same problem is occuring. Or do you mean linking gdb with
pthread somehow?

Thanks,
John


  reply	other threads:[~2007-06-19 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 20:22 John Bates
2007-06-19 20:28 ` Daniel Jacobowitz
2007-06-19 20:56   ` John Bates [this message]
2007-06-19 21:04     ` Daniel Jacobowitz
2007-06-25 23:20 ` John Bates
2007-06-26 17:06   ` Jim Blandy
2007-06-26 18:48     ` John Bates
2007-06-26 23:52       ` Jim Blandy
2009-04-09 18:48       ` ajitnayak
     [not found]         ` <20090409200657.GA22217@host0.dyn.jankratochvil.net>
     [not found]           ` <b1bfafd50904130735x32d369a0ub4005758d7d9e2c8@mail.gmail.com>
2009-04-13 19:00             ` Jan Kratochvil

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=a4c7fade0706191356j2b2a93cev45ea2795d52c5a64@mail.gmail.com \
    --to=johnnybates@gmail.com \
    --cc=gdb@sourceware.org \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox