public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Ian Lance Taylor <>
Cc: Daniel Jacobowitz <>, Frysk List <>
Subject: Re: Roadmap beginnings
Date: Mon, 14 Jul 2008 17:35:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Ian Lance Taylor's message of "Mon\, 14 Jul 2008 10\:18\:53 -0700")

>>>>> "Ian" == Ian Lance Taylor <> writes:

Tom> I'm looking around a bit to see if I can find specifics of what
Tom> is wrong.

Ian> I don't know if this counts as "expression parsing," but the most
Ian> obvious problems that I encounter are the difficulties in working with
Ian> STL objects.  Given "std::vector<T> v", I can't do "print v[0]".
Ian> Given "std::vector<T>::iterator p", I can't do "print *p".  That is
Ian> minimal required functionality for good C++ debugging.  This needs to
Ian> work smoothly for STL types and for user defined types.

Thanks.  I remember you mentioning this at the Summit, but I'd
forgotten when sending the email.

Ian> A related problem, which I don't know how to solve, is that many
Ian> simple C++ accessors get inlined, and are not available when
Ian> debugging.  This makes it vastly more difficult to debug optimized C++
Ian> programs (indeed, this problem is more serious for me in practice than
Ian> the debuginfo problems discussed at the summit).

I have seen a few ideas kicked around:

1. Always emit the accessors out-of-line.

2. Emit DWARF code corresponding to the accessors.

3. Write Python code equivalent to the accessors and arrange for the
   debugger to invoke it in the appropriate situations.

#1 seems like the obvious choice, aside from code size problems.  Are
those severe?


  parent reply	other threads:[~2008-07-14 17:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 19:53 Tom Tromey
2008-07-11 20:56 ` Jan Kratochvil
2008-07-11 21:37   ` Tom Tromey
2008-07-11 21:54     ` Daniel Jacobowitz
2008-07-11 23:11   ` Kris Van Hees
2008-07-11 21:53 ` Daniel Jacobowitz
2008-07-14 16:34   ` Tom Tromey
2008-07-14 16:45     ` Daniel Jacobowitz
2008-07-14 16:58       ` Phil Muldoon
2008-07-14 17:09         ` Daniel Jacobowitz
2008-07-14 17:19     ` Ian Lance Taylor
2008-07-14 17:34       ` Daniel Jacobowitz
2008-07-14 18:04         ` Tom Tromey
2008-07-14 18:12           ` Daniel Jacobowitz
2008-07-14 18:11         ` Ian Lance Taylor
2008-07-14 17:35       ` Tom Tromey [this message]
2008-07-14 18:13         ` Ian Lance Taylor
2008-07-22 20:29   ` Debugger Work (Was: Roadmap beginnings) Tom Tromey
2008-07-11 22:48 ` Roadmap beginnings Phil Muldoon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).