Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Veksler <mveksler@techunix.technion.ac.il>
To: Frederic RISS <frederic.riss@st.com>
Cc: gdb@sourceware.org, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Get versioned minsyms from dynamic symtab (Was: Re: How to call  operator<< functions?)
Date: Thu, 31 Aug 2006 12:09:00 -0000	[thread overview]
Message-ID: <44F6D16B.7090001@tx.technion.ac.il> (raw)
In-Reply-To: <1157024034.3429.303.camel@crx549.cro.st.com>

Frederic RISS wrote:
> On Linux, versioned ELF symbols are stored in the static symtab with an
> (@)@VERSION suffix. We store such symbols with the suffix and thus fail
> to find them when looking up the real name.
>
> This causes failures such as the one described here:
> http://www.sourceware.org/ml/gdb/2006-08/msg00244.html
>
> In the general case, GDB doesn't use the dynamic symtab because it
> contains usually only a subset of the static table information. The
> attached patch make GDB store dynamic versioned symbols. 
>
> Maybe this is harvests too much symbols, and we should limit it to the
> dynamic symbols of the main executable. It's easy enough to do, we just
> need to pass the 'mainline' flag to elf_symfile_read from
> elf_symtab_read. 
>
> I've no idea if this could break something on non-Linux platforms, I've
> just tested on x86-linux.
>
> I'm also attaching a little testsuite patch that fails for me on current
> GDB and works with the patch.
>
> Opinions?
>   
Great, now std::cout does not cause crashes. Still there is the problem of

    (gdb) p std::cout
    $1 = <incomplete type>

But that's unrelated, right?
The problem with this result is that it sometimes confuses GDB as 
described at the end of:
  http://sources.redhat.com/ml/gdb/2006-08/msg00271.html

  Michael


  reply	other threads:[~2006-08-31 12:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 10:11 How to call operator<< functions? Michael Veksler
2006-08-30 11:13 ` Frederic RISS
2006-08-30 13:30   ` Frederic RISS
2006-08-30 13:40     ` Breakpoint Handling in GDB Veenu Verma (AS/EAB)
2006-08-30 13:43       ` Daniel Jacobowitz
2006-08-30 20:30       ` Michael Snyder
2006-08-31 11:34     ` Get versioned minsyms from dynamic symtab (Was: Re: How to call operator<< functions?) Frederic RISS
2006-08-31 12:09       ` Michael Veksler [this message]
2006-08-31 12:26         ` Frederic RISS
2006-08-31 13:02           ` Michael Veksler
2006-08-31 13:23             ` Frederic RISS
2006-08-31 16:48               ` Frederic RISS
2006-08-31 16:57                 ` Daniel Jacobowitz
2006-08-31 17:41                   ` Frédéric Riss
2006-08-31 17:45                     ` Daniel Jacobowitz
2006-08-31 19:48                   ` Michael Veksler
2006-08-31 19:52                     ` Daniel Jacobowitz
2006-08-30 12:46 ` How to call operator<< functions? Daniel Jacobowitz
2006-08-30 20:05   ` Michael Veksler
2006-08-30 20:24     ` Daniel Jacobowitz
2006-08-30 20:45       ` Michael Veksler
2006-08-30 20:54         ` Daniel Jacobowitz
2006-08-31 12:05           ` Michael Veksler

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=44F6D16B.7090001@tx.technion.ac.il \
    --to=mveksler@techunix.technion.ac.il \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sourceware.org \
    --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