From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] ia64: incorrect breakpoint save/restore with L-type instruction at slot 1
Date: Tue, 29 Sep 2009 19:14:00 -0000 [thread overview]
Message-ID: <20090929191401.GC6362@adacore.com> (raw)
In-Reply-To: <20090929185518.GA598@host0.dyn.jankratochvil.net>
This is great work, thanks!
> gdb/testsuite/
> 2009-09-29 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/breakpoint-shadow.exp: Move the ia64 part into ...
> * gdb.arch/ia64-breakpoint-shadow.exp, ... a new file, with new tests.
> * gdb.arch/ia64-breakpoint-shadow.S: New file.
Just one nit, I think. Shouldn't we disassemble bundle, rather than
main? Pre-approved, HEAD and branch.
--
Joel
next prev parent reply other threads:[~2009-09-29 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 20:48 Joel Brobecker
2009-09-26 21:57 ` Jan Kratochvil
2009-09-29 0:16 ` Joel Brobecker
2009-09-29 1:31 ` Joel Brobecker
2009-09-29 18:55 ` Jan Kratochvil
2009-09-29 19:14 ` Joel Brobecker [this message]
2009-09-29 19:29 ` Jan Kratochvil
2009-09-29 0:00 ` 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=20090929191401.GC6362@adacore.com \
--to=brobecker@adacore.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