From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: -stack-list-frames HIGH_FRAME changes
Date: Thu, 07 Sep 2006 16:10:00 -0000 [thread overview]
Message-ID: <20060907161020.GA9198@nevyn.them.org> (raw)
In-Reply-To: <200605051838.20652.ghost@cs.msu.su>
On Fri, May 05, 2006 at 06:38:19PM +0400, Vladimir Prus wrote:
> In any case, there's revised patch:
>
> ./Changelog:
> 2006-05-05 Vladimir Prus <ghost@lvk.cs.msu.su>
>
> * mi/mi-cmd-stack.c (mi_cmd_stack_list_frames): Don't emit error
> if high requested frame number is larger then number of available
> frames.
>
>
> doc/ChangeLog
> 2006-05-05 Vladimir Prus <ghost@lvk.cs.msu.su>
>
> * gdb.texinfo (GDB/MI Stack Manipulation): Mention that
> -stack-list-locals HIGH_FRAME argument can be larger then the
> actual number of frames.
>
>
> testsuite/ChangeLog
>
> 2006-05-05 Vladimir Prus <ghost@lvk.cs.msu.su>
>
> * gdb.mi/mi-stack.exp (test_stack_frame_listing): Test that
> HIGH_FRAME argument to -stack-list-locals can be larger than
> the number of frames.
This patch is OK. Sorry for forgetting about it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-09-07 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 7:54 Vladimir Prus
2006-05-05 10:30 ` Eli Zaretskii
2006-05-05 13:51 ` Daniel Jacobowitz
2006-05-05 14:39 ` Vladimir Prus
2006-05-05 14:53 ` Daniel Jacobowitz
2006-05-05 19:20 ` Jim Blandy
2006-05-05 15:46 ` Bob Rossi
2006-05-05 14:52 ` Daniel Jacobowitz
2006-09-07 16:10 ` Daniel Jacobowitz [this message]
2006-09-07 16:41 ` Vladimir Prus
2006-05-05 21:13 ` Eli Zaretskii
2006-09-07 16:10 ` Vladimir Prus
2006-09-07 22:37 Nick Roberts
2006-09-07 23:10 ` Daniel Jacobowitz
2006-09-08 6:28 ` Vladimir Prus
2006-09-08 8:30 ` Nick Roberts
2006-09-08 8:39 ` Vladimir Prus
2006-09-08 14:33 ` Daniel Jacobowitz
2006-09-08 16:37 ` Eli Zaretskii
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=20060907161020.GA9198@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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