From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix crash on DWARF C++ forward reference
Date: Fri, 22 Jan 2010 02:06:00 -0000 [thread overview]
Message-ID: <20100122020552.GA29916@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3d412vrsx.fsf@fleche.redhat.com>
On Fri, 22 Jan 2010 02:42:22 +0100, Tom Tromey wrote:
> I also came up with a patch. What do you think of the appended?
OK, it is a better approach. I cannot find a countercase.
Regards,
Jan
next prev parent reply other threads:[~2010-01-22 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 1:02 Jan Kratochvil
2010-01-22 1:42 ` Tom Tromey
2010-01-22 2:06 ` Jan Kratochvil [this message]
2010-01-22 17:06 ` Tom Tromey
2010-02-19 15:54 ` Andreas Schwab
2010-02-19 19:16 ` [obv] m68k fix of gdb.dwarf2/member-ptr-forwardref.S [Re: [patch] Fix crash on DWARF C++ forward reference] Jan Kratochvil
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=20100122020552.GA29916@host0.dyn.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