public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "lm at zork dot pl" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/11803] TLS (__thread) on static class member variable trips assert
Date: Mon, 13 Sep 2010 15:41:00 -0000	[thread overview]
Message-ID: <20100913154102.11284.qmail@sourceware.org> (raw)
In-Reply-To: <20100709204412.11803.jacob@durbatuluk.us>


------- Additional Comments From lm at zork dot pl  2010-09-13 15:41 -------
(In reply to comment #1)
> From what I can tell, TLS needs registers, but not actually a frame
> in the gdb internals sense.  Looking through the code paths, I don't
> see anything actually using a frame.  And, it seems to me that these
> frame checks are actually gdb internal consistency checks.
> So, I think it is probably safe to change needs_frame_tls_address.
> 

I just run into this on i686. I verified test program with gdb 7.2.50.20100913-
cvs and gcc-4.5.1 under linux it breaks in the same way.

In my case this bug breaks all IDE front ends when debugging wxWidgets they try 
to access all local variables when stepping through code, and wxString class has 
thread-local static class variable.

Changing needs_frame_tls_address fixes this problem.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11803

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-09-13 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 20:44 [Bug exp/11803] New: " jacob at durbatuluk dot us
2010-07-16 18:02 ` [Bug exp/11803] " tromey at redhat dot com
2010-09-13 15:41 ` lm at zork dot pl [this message]
2010-09-14  7:33 ` lm at zork dot pl
2010-09-14 17:47 ` tromey at redhat dot com
2010-09-14 19:10 ` tromey at redhat dot com

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=20100913154102.11284.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).