From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Assert leftover cleanups in TRY_CATCH
Date: Tue, 07 May 2013 18:00:00 -0000 [thread overview]
Message-ID: <20130507180017.GA23925@host2.jankratochvil.net> (raw)
In-Reply-To: <87mws6vovt.fsf@fleche.redhat.com>
On Tue, 07 May 2013 16:35:50 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Jan> GDB still is barely usable for real C++ application debugging,
> Jan> debugging multiple virtual class inheritance does not work
>
> Could you make sure to file bugs for this?
> I was surprised to hear there are still bugs here.
Filed (seems to be harmless now but it looked as broken to me):
virtual inheritance: __in_chrg and __vtt_parm
http://sourceware.org/bugzilla/show_bug.cgi?id=15437
The other problem with "double-pointers" is in fact an already filed one:
"set print object on" + printing variables of type: a reference to derived class.
http://sourceware.org/bugzilla/show_bug.cgi?id=15401
Jan
next prev parent reply other threads:[~2013-05-07 18:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 16:57 Jan Kratochvil
2013-05-02 17:02 ` Pedro Alves
2013-05-05 16:56 ` [commit] " Jan Kratochvil
2013-05-06 17:57 ` Tom Tromey
2013-05-06 18:18 ` Jan Kratochvil
2013-05-06 18:50 ` Tom Tromey
2013-05-07 1:47 ` Jan Kratochvil
2013-05-07 4:37 ` Doug Evans
2013-05-07 4:49 ` Doug Evans
2013-05-07 15:24 ` Jan Kratochvil
2013-05-15 0:13 ` Benchmarking (was Re: [patch 2/2] Assert leftover cleanups in TRY_CATCH) Stan Shebs
2013-05-15 17:00 ` Doug Evans
2013-05-22 20:51 ` Tom Tromey
2013-05-07 14:36 ` [patch 2/2] Assert leftover cleanups in TRY_CATCH Tom Tromey
2013-05-07 18:00 ` Jan Kratochvil [this message]
2013-05-07 6:23 ` Joel Brobecker
2013-05-07 14:20 ` [patch] " Jan Kratochvil
2013-05-14 20:39 ` [commit] " Jan Kratochvil
2013-05-07 14:40 ` Tom Tromey
2013-05-07 14:55 ` Jan Kratochvil
2013-05-07 15:26 ` Tom Tromey
2013-05-08 5:54 ` Joel Brobecker
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=20130507180017.GA23925@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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