public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "john at calva dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/8588] symbols present in multiple files are displayed wrongly Date: Sat, 02 Feb 2013 11:27:00 -0000 [thread overview] Message-ID: <bug-8588-4717-4FZsrqC4G2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-8588-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=8588 --- Comment #6 from John Hughes <john at calva dot com> 2013-02-02 11:27:47 UTC --- On 02/01/2013 10:56 PM, naesten at gmail dot com wrote: > This leaves me wondering: Is this really architecture-dependent, or is it just > due to chance (different addresses, hash collisions, etc.) that it works for me > and not for you? I guess you're on x86? My machines are amd64 > > My questions for you are: > > 1. What version of libc6-dev do you have installed? ii gcc 4:4.7.2-1 amd64 GNU C compiler ii gdb 7.4.1-3 amd64 The GNU Debugger ii libc6-dev:amd6 2.13-38 amd64 Embedded GNU C Library: Developme > > 2. What do you get for "info variables optind"? > Not at all the same as you: (gdb) info variables optind All variables matching regular expression "optind": Non-debugging symbols: 0x0000000000600930 optind@@GLIBC_2.2.5 Interesting - "non-debugging symbols"? Maybe I should install libc6-dbg? Well, with libc6-dbg I get different output from info variables: All variables matching regular expression "optind": File getopt.c: int optind; Non-debugging symbols: 0x0000000000600930 optind@@GLIBC_2.2.5 But "p" still doesn't show the version I want: (gdb) p &optind $1 = (int *) 0x7ffff7dd7130 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-02-02 11:27 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-8588-4717@http.sourceware.org/bugzilla/> 2013-01-27 0:30 ` naesten at gmail dot com 2013-01-28 3:26 ` naesten at gmail dot com 2013-01-29 23:56 ` naesten at gmail dot com 2013-01-30 9:08 ` john at calva dot com 2013-02-01 21:56 ` naesten at gmail dot com 2013-02-01 22:56 ` naesten at gmail dot com 2013-02-02 11:27 ` john at calva dot com [this message] 2013-02-04 17:43 ` tromey at redhat dot com 2013-02-04 20:15 ` naesten at gmail dot com 2013-02-04 20:18 ` naesten at gmail dot com 2013-02-04 20:18 ` naesten at gmail dot com 2013-09-16 15:40 ` tromey at redhat dot com 2014-11-06 18:41 ` pguttmann at bloomberg dot net 2021-10-18 17:39 ` peter.weber at flapflap dot eu
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=bug-8588-4717-4FZsrqC4G2@http.sourceware.org/bugzilla/ \ --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: linkBe 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).