This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[ping 2]: [PATCH 0/3] Select the current frame in command tdump.

From: Yao Qi <yao at codesourcery dot com>
To: <gdb-patches at sourceware dot org>
Date: Mon, 29 Jul 2013 17:30:25 +0800
Subject: [ping 2]: [PATCH 0/3] Select the current frame in command tdump.
References: <1372341726-5485-1-git-send-email-yao at codesourcery dot com> <51EC871C dot 6050904 at codesourcery dot com>

On 07/22/2013 09:13 AM, Yao Qi wrote:

Command 'tdump' should be run on the current stack frame instead of
>the selected stack frame.  The patch 3/3 is to change to the current
>stack trace when executing command 'tdump'.  When writing test case
>for this change, I did some cleanups in gdb.trace/backtrace.exp (in
>patch 1/3) and get the test result unique (patch 2/3).
>
>Regression tested on x86_64-linux.

Ping.http://sourceware.org/ml/gdb-patches/2013-06/msg00817.html


Ping 2.  http://sourceware.org/ml/gdb-patches/2013-06/msg00817.html

--
Yao (éå)

References:
- Re: [PATCH 0/3] Select the current frame in command tdump.
  - From: Yao Qi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]