Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/3] Select the current frame in command tdump.
Date: Thu, 27 Jun 2013 14:02:00 -0000	[thread overview]
Message-ID: <1372341726-5485-1-git-send-email-yao@codesourcery.com> (raw)

Hi,
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.

*** BLURB HERE ***

Yao Qi (3):
  Tweak gdb.trace/backtrace.exp
  Make test result of gdb.trace/backtrace.exp unique
  Select the current frame in command tdump.

 gdb/testsuite/gdb.trace/backtrace.exp |   86 ++++++++++++++++++++-------------
 gdb/tracepoint.c                      |    6 ++
 2 files changed, 59 insertions(+), 33 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2013-06-27 14:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 14:02 Yao Qi [this message]
2013-06-27 14:02 ` [PATCH 2/3] Make test result of gdb.trace/backtrace.exp unique Yao Qi
2013-07-29 15:44   ` Pedro Alves
2013-06-27 14:02 ` [PATCH 1/3] Tweak gdb.trace/backtrace.exp Yao Qi
2013-07-29 15:44   ` Pedro Alves
2013-06-27 14:22 ` [PATCH 3/3] Select the current frame in command tdump Yao Qi
2013-07-29 15:44   ` Pedro Alves
2013-07-30 13:23     ` Yao Qi
2013-07-30 13:31       ` Pedro Alves
2013-07-31  0:47         ` Yao Qi
2013-07-22  1:13 ` [PATCH 0/3] " Yao Qi
2013-07-29  9:31   ` [ping 2]: " Yao Qi

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=1372341726-5485-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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