From: Daniel Jacobowitz <drow@false.org>
To: Michael Veksler <mveksler@techunix.technion.ac.il>
Cc: Frederic RISS <frederic.riss@st.com>, gdb@sourceware.org
Subject: Re: Get versioned minsyms from dynamic symtab (Was: Re: How to call operator<< functions?)
Date: Thu, 31 Aug 2006 19:52:00 -0000 [thread overview]
Message-ID: <20060831195245.GA12447@nevyn.them.org> (raw)
In-Reply-To: <44F73D1B.6010507@tx.technion.ac.il>
On Thu, Aug 31, 2006 at 10:48:43PM +0300, Michael Veksler wrote:
> >This is a deliberate choice on GCC's part, to reduce overly excessive
> >debug information. There've been arguments about it in the past. My
> >
> From bits/ostream.tcc header file:
> // Inhibit implicit instantiations for required instantiations,
> // which are defined via explicit instantiations elsewhere.
> // NB: This syntax is a GNU extension.
> #if _GLIBCXX_EXTERN_TEMPLATE
> extern template class basic_ostream<char>;
No, that's irrelevant to what I was talking about; some parts of the
debug info are done only with the class's key method. But...
> >feeling is that we will end up with something like a -gfull argument
> >to force the extra information to be emitted. GDB needs to work as
> >well as possible anyway.
> >
> >
> Reading it more, one can force full instantiation of ostream:
> g++ -g -D_GLIBCXX_EXTERN_TEMPLATE=0 myCout.cpp cout-gdb.cpp
> Now everything works, and it is not that much bigger.
...this causes the key method to be in the header for every compilation
unit, IIUC.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-31 19:52 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
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 [this message]
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=20060831195245.GA12447@nevyn.them.org \
--to=drow@false.org \
--cc=frederic.riss@st.com \
--cc=gdb@sourceware.org \
--cc=mveksler@techunix.technion.ac.il \
/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