Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: GDB List <gdb@sourceware.org>
Subject: Re: C++ Typedefs and symbol tables
Date: Mon, 20 Aug 2007 18:12:00 -0000	[thread overview]
Message-ID: <46C9D968.40809@st.com> (raw)
In-Reply-To: <20070820174920.GA12384@caradoc.them.org>

Daniel Jacobowitz wrote:
> Symbols come from .debug_info and have type information.  minsyms come
> from the ELF .symtab section, and do not.

Ah, OK. How do I determine this, and how do I get it to use the proper 
symbols if it has chosen the wrong ones?

I know that the debug info contains the definition given in the source - 
at least for one example I looked at, anyway. It couldn't have arrived 
at the version given by 'info functions' without canonicalizing the 
debug info, so I assume it must be using the (already canonical) minsyms 
only.

> 2-3 typenames is not typical, in C++ programs.  It added around 30%
> time in my testing.

Oh? I'm talking about converting something like

	Int32 f(Bp,Int16)
  to
	int f(B*,short)

(where Bp is an example of a typedef), and only for parameters given to 
breakpoint commands and the like.

There's only 3 types in that (four if you count the function type), and 
breakpoint commands wouldn't come up _too_ often, so surely it couldn't 
take that much time?

Surely we are talking at cross-purposes?

Andrew


  reply	other threads:[~2007-08-20 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 17:11 Andrew STUBBS
2007-08-20 17:18 ` Daniel Jacobowitz
2007-08-20 17:35   ` Andrew STUBBS
2007-08-20 17:49     ` Daniel Jacobowitz
2007-08-20 18:12       ` Andrew STUBBS [this message]
2007-08-20 18:23         ` 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=46C9D968.40809@st.com \
    --to=andrew.stubbs@st.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