From: Ian Lance Taylor <iant@google.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Tom Tromey <tromey@redhat.com>, Frysk List <frysk@sourceware.org>
Subject: Re: Roadmap beginnings
Date: Mon, 14 Jul 2008 18:11:00 -0000 [thread overview]
Message-ID: <m3abgkz69z.fsf@google.com> (raw)
In-Reply-To: <20080714173355.GA9326@caradoc.them.org> (Daniel Jacobowitz's message of "Mon\, 14 Jul 2008 13\:33\:55 -0400")
Daniel Jacobowitz <drow@false.org> writes:
>> A related problem, which I don't know how to solve, is that many
>> simple C++ accessors get inlined, and are not available when
>> debugging. This makes it vastly more difficult to debug optimized C++
>> programs (indeed, this problem is more serious for me in practice than
>> the debuginfo problems discussed at the summit).
>
> Actually, see above. I assumed that was your problem with the STL
> operators. If there are other problems, please let us know - maybe
> after Tom finishes the Bugzilla migration he's got almost done :-)
No, I see this problem even when debugging programs which are compiled
without optimization. This is with the gdb shipped with FC8, based on
6.6. It may well have improved since then.
Ian
next prev parent reply other threads:[~2008-07-14 18:11 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 [this message]
2008-07-14 17:35 ` Tom Tromey
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:
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=m3abgkz69z.fsf@google.com \
--to=iant@google.com \
--cc=drow@false.org \
--cc=frysk@sourceware.org \
--cc=tromey@redhat.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).