From: Andreas Schwab <schwab@linux-m68k.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] GDB/MI: crash printing "_task" (Ada) argument
Date: Thu, 19 Jul 2012 07:53:00 -0000 [thread overview]
Message-ID: <m2a9ywkx0b.fsf@igel.home> (raw)
In-Reply-To: <20120203073352.GI31383@adacore.com> (Joel Brobecker's message of "Fri, 3 Feb 2012 11:33:52 +0400")
Joel Brobecker <brobecker@adacore.com> writes:
> +# Verify that "-stack-list-arguments" does not cause the debugger to
> +# crash when printing the arguments of frame 1 (due to the internally-
> +# generated argument "_task").
> +mi_gdb_test "-stack-list-arguments 1" \
> + "\\^done,stack-args=\\\[frame=\{level=\"0\",args=\\\[\\\]\},frame=\{level=\"1\",args=\\\[\{name=\"<_task>\",value=\"$hex\"\}\\\]\},frame=\{level=\"2\",args=\\\[\\\]\}.*" \
> + "-stack-list-arguments 1"
> +
Expecting: ^(-stack-list-arguments 1[
]+)?(\^done,stack-args=\[frame={level="0",args=\[\]},frame={level="1",args=\[{name="<_task>",value="0x[0-9A-Fa-f]+"}\]},frame={level="2",args=\[\]}.*[
]+[(]gdb[)]
[ ]*)
-stack-list-arguments 1
^done,stack-args=[frame={level="0",args=[]},frame={level="1",args=[{name="<_task>",value="0x1005a9b8"}]},frame={level="2",args=[{name="self_id",value="0x1005a9c8"}]},frame={level="3",args=[]},frame={level="4",args=[]}]
(gdb)
FAIL: gdb.ada/mi_task_arg.exp: -stack-list-arguments 1
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 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 7:01 Joel Brobecker
2012-01-30 19:58 ` Tom Tromey
2012-01-30 20:07 ` Tom Tromey
2012-02-03 7:34 ` Joel Brobecker
2012-07-19 7:53 ` 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=m2a9ywkx0b.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=brobecker@adacore.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