Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH/RFC] Include value of default-collect in breakpoint/tracepoint   list
Date: Fri, 09 Apr 2010 00:55:00 -0000	[thread overview]
Message-ID: <4BBE7AEB.4090004@codesourcery.com> (raw)
In-Reply-To: <4BBA7264.5060109@codesourcery.com>

I cleverly managed to regression-test the wrong tree - leftover 
default-collect settings can affect info output, so this patch cleans up 
after testing.  Committed to trunk.

Stan

2010-04-08  Stan Shebs  <stan@codesourcery.com>

    * gdb.trace/actions.exp: Clear default-collect.
    * gdb.trace/save-trace.exp: Clear default-collect.

Index: gdb.trace/actions.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.trace/actions.exp,v
retrieving revision 1.17
diff -p -r1.17 actions.exp
*** gdb.trace/actions.exp    1 Apr 2010 22:57:25 -0000    1.17
--- gdb.trace/actions.exp    9 Apr 2010 00:49:20 -0000
*************** gdb_test "show default-collect" \
*** 204,209 ****
--- 204,213 ----
      "The list of expressions to collect by default is \"gdb_char_test, 
gdb_long_test - 100\"..*" \
      "5.9b: show default-collect"
 
+ gdb_test "set default-collect" \
+     "" \
+     "5.9c: set default-collect"
+
  # 5.10 teval
 
  gdb_test "tvariable \$tsv" \
Index: gdb.trace/save-trace.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.trace/save-trace.exp,v
retrieving revision 1.15
diff -p -r1.15 save-trace.exp
*** gdb.trace/save-trace.exp    31 Mar 2010 17:59:49 -0000    1.15
--- gdb.trace/save-trace.exp    9 Apr 2010 00:49:20 -0000
*************** gdb_test "save-tracepoints savetrace.tr"
*** 135,140 ****
--- 135,141 ----
  # 10.2 Read back tracepoint definitions
 
  gdb_delete_tracepoints
+ gdb_test "set default-collect" "" "10.2: clear default-collect"
  gdb_test "info tracepoints" "No tracepoints." "10.2: delete tracepoints"
  gdb_test "source savetrace.tr" \
      "Tracepoint \[0-9\]+ at .*" \
*************** gdb_test "save-tracepoints $objdir/savet
*** 151,156 ****
--- 152,158 ----
      "10.3: save tracepoint definitions, full path"
 
  gdb_delete_tracepoints
+ gdb_test "set default-collect" "" "10.3: clear default-collect"
  gdb_test "info tracepoints" "No tracepoints." "10.3: delete tracepoints"
  gdb_test "source $objdir/savetrace.tr" \
      "Tracepoint \[0-9\]+ at .*" \


      parent reply	other threads:[~2010-04-09  0:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 23:30 Stan Shebs
2010-04-07 19:56 ` Tom Tromey
2010-04-08 23:18   ` Stan Shebs
2010-04-09  0:55 ` Stan Shebs [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=4BBE7AEB.4090004@codesourcery.com \
    --to=stan@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