From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: New test gdb.dwarf2/dw2-aranges.exp
Date: Fri, 23 Jul 2010 22:04:00 -0000 [thread overview]
Message-ID: <m3aaph3ldy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100723210833.GA12568@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 23 Jul 2010 23:08:33 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> this patch was written for a former bug in
Jan> [archer-tromey-delayed-symfile]. This branch is probably going to
Jan> be dropped but I thought that patch could go for FSF GDB. OTOH FSF
Jan> GDB had never this bug.
Jan> OK to check-in?
I don't think we need this, because CVS gdb doesn't read .debug_aranges,
and I don't think we're going to add that.
If we do end up needing that feature in the future, I think we can
easily extract the necessary code from the branch. So, I would
recommend committing this there.
Tom
next prev parent reply other threads:[~2010-07-23 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 21:08 Jan Kratochvil
2010-07-23 22:04 ` Tom Tromey [this message]
2010-07-23 22:10 ` 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=m3aaph3ldy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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