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]

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


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


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