From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fix 'info reg' output
Date: Thu, 19 Jul 2012 09:22:00 -0000 [thread overview]
Message-ID: <m28vegjebj.fsf@igel.home> (raw)
In-Reply-To: <87ipj7nc5y.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 15 Feb 2012 12:12:41 -0700")
Tom Tromey <tromey@redhat.com> writes:
> +# Regression test for
> +# http://sourceware.org/bugzilla/show_bug.cgi?id=12659
> +gdb_test "info register pc fp" \
> + "pc: ${valueof_pc}\[\r\n\]+fp: ${valueof_fp}\[\r\n\]+"
>
info register pc fp
pc 0x100005d0 0x100005d0 <main+20>
fp: 0xfffffffd6e0
(gdb) FAIL: gdb.base/pc-fp.exp: info register pc fp
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2012-07-19 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 19:30 Tom Tromey
2012-07-19 9:22 ` Andreas Schwab [this message]
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=m28vegjebj.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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