From: Brian Dessent <brian@dessent.net>
To: gdb@sourceware.org
Subject: Re: Why type = <data variable, no debug info>?
Date: Sat, 21 Oct 2006 03:51:00 -0000 [thread overview]
Message-ID: <4539992E.626AAE3A@dessent.net> (raw)
In-Reply-To: <200610210620.24201.munzirtaha@gmail.com>
"Munzir Taha (???? ??)" wrote:
>
> Hi, in this small program logic tells me that errno and n should have the same
> value displayed in gdb. Am I missing something obvious?
You're probably running into the fact that on modern glibc errno is a
TLS symbol, not a regular one. This means it can take on a different
value in each thread, and thus is accessed through an indirection.
You might get better debugging ability if you compile with -ggdb3
instead of just -g, which gives gdb some additional information. I
believe that without any debug information in the binary, gdb cannot do
anything about TLS symbols, but I'm not sure. See also the proposed
patch <http://sourceware.org/ml/gdb-patches/2006-08/threads.html#00187>
and/or <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185337>.
Brian
next prev parent reply other threads:[~2006-10-21 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 3:20 Munzir Taha (منذر طه)
2006-10-21 3:51 ` Brian Dessent [this message]
2006-10-21 4:44 ` Munzir Taha (منذر طه)
2006-10-21 5:13 ` Daniel Jacobowitz
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=4539992E.626AAE3A@dessent.net \
--to=brian@dessent.net \
--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