From: Frederic RISS <frederic.riss@st.com>
To: Michael Veksler <mveksler@techunix.technion.ac.il>
Cc: gdb@sourceware.org
Subject: Re: Get versioned minsyms from dynamic symtab (Was: Re: How to call operator<< functions?)
Date: Thu, 31 Aug 2006 12:26:00 -0000 [thread overview]
Message-ID: <1157027172.3429.309.camel@crx549.cro.st.com> (raw)
In-Reply-To: <44F6D16B.7090001@tx.technion.ac.il>
On Thu, 2006-08-31 at 15:09 +0300, Michael Veksler wrote:
> 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?
Yes, unrelated.
This should work if you've got a version of libstdc++ compiled with
debug info. If you don't, then GDB can't find std::cout's type. This
works for me once the library is loaded (i.e. once the inferior is
running):
(gdb) p std::cout
$1 = <incomplete type>
(gdb) ptype std::cout
type = struct std::basic_ostream<char,std::char_traits<char> > {
<incomplete type>
}
(gdb) start
Breakpoint 1 at 0x8048703: file cout.cc, line 11.
Starting program: /home/rf23/tmp/cout/a.out
main () at cout.cc:11
11 std::cout << "&std::cout is " << &std::cout << std::endl;
(gdb) ptype std::cout
type = class std::basic_ostream<char,std::char_traits<char> >
: public virtual std::basic_ios<char,std::char_traits<char> > {
public:
void basic_ostream(int, const void **,
class std::basic_streambuf<char,std::char_traits<char> > *);
protected:
void basic_ostream(int, const void **);
public:
~basic_ostream(int, const void **);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(std::ostream& (*)(std::ostream&));
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(std::basic_ios<char, std::char_traits<char> >& (*)(std::basic_ios<char, std::char_traits<char> >&));
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(std::ios_base& (*)(std::ios_base&));
class std::basic_ostream<char,std::char_traits<char> > & operator<<(long);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(unsigned long);
class std::basic_ostream<char,std::char_traits<char> > & operator<<(bool);
class std::basic_ostream<char,std::char_traits<char> > & operator<<(short);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(unsigned short);
class std::basic_ostream<char,std::char_traits<char> > & operator<<(int);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(unsigned int);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(long long);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(unsigned long long);
class std::basic_ostream<char,std::char_traits<char> >
& operator<<(double);
class std::basic_ostream<char,std::char_traits<char> > & operator<<(float);
class std::basic_ostream<char,std::char_traits<char> >
---Type <return> to continue, or q <return> to quit---q
& operator<<(long douQuit
(gdb) q
next prev parent reply other threads:[~2006-08-31 12:26 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 [this message]
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=1157027172.3429.309.camel@crx549.cro.st.com \
--to=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