From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: vicshen@gmail.com, gdb@sourceware.org
Subject: Re: gdb cannot understand some type with STL
Date: Sat, 22 Dec 2007 17:40:00 -0000 [thread overview]
Message-ID: <ud4syiq5s.fsf@gnu.org> (raw)
In-Reply-To: <20071222173507.GA21728@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 22 Dec 2007 12:35:07 -0500)
> Date: Sat, 22 Dec 2007 12:35:07 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sourceware.org
>
> It's going to be a std::list<int, std::allocator<int> > or something
> like that.
In which case "whatis 'std::list TAB" (note the single quote) should
complete the correct text to type, right?
next prev parent reply other threads:[~2007-12-22 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 5:24 jian shen
2007-12-22 10:18 ` Eli Zaretskii
2007-12-22 10:35 ` jian shen
2007-12-22 17:35 ` Daniel Jacobowitz
2007-12-22 17:40 ` Eli Zaretskii [this message]
2007-12-22 17:45 ` Daniel Jacobowitz
2007-12-23 2:27 ` jian shen
2008-01-02 17:29 ` Gordon Prieur
2008-01-02 18:04 ` Daniel Jacobowitz
2007-12-23 2:26 ` jian shen
2008-01-03 22:23 Nick Roberts
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=ud4syiq5s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=vicshen@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).