public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Pedro Alves <palves@redhat.com>, <eliz@gnu.org>,
	<gdb-patches@sourceware.org>
Subject: Re: [PATCH, doc RFA] Add "skip regexp"
Date: Wed, 02 Mar 2016 23:20:00 -0000	[thread overview]
Message-ID: <001a1145617e604203052d191f01@google.com> (raw)

Simon Marchi writes:
  > On 16-02-16 08:07 PM, Doug Evans wrote:
  > > +# Test -fi + -fu.
  > > +
  > > +if ![runto_main] {
  > > +    fail "Can't run to main"
  > > +    return
  > > +}
  > > +
  > > +set test "step using -fi + -fu"
  > > +gdb_test_no_output "skip delete"
  > > +gdb_test "skip -fi skip1.c -fu test_skip" \
  > > +    "Function test_skip in file skip1.c will be skipped when  
stepping\."
  > > +gdb_breakpoint "test_skip_file_and_function"
  > > +gdb_breakpoint "end_test_skip_file_and_function"
  > > +gdb_test "call test_skip_file_and_function ()" "silently stop."
  >
  > Hi Doug,
  >
  > I just saw a failure of this test on a target that doesn't have inferior  
calls.  It
  > seems to me like the function call isn't fundamental to the test and it  
could be
  > avoided by organizing things differently.  What do you think?
  >
  > Otherwise, we would need to add a
  >
  >   if [target_info exists gdb,cannot_call_functions] {

Bleah, righto.

Fix forthcoming.
I need to cleanup skip.exp first.

             reply	other threads:[~2016-03-02 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 23:20 Doug Evans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-15 19:45 Doug Evans
2016-03-03 19:21 Doug Evans
2016-03-03 20:40 ` Simon Marchi
2016-02-23 21:36 Doug Evans
2016-02-24  9:54 ` Joel Brobecker
2016-02-24 18:21   ` Doug Evans
2016-02-17  1:07 Doug Evans
2016-02-17 16:07 ` Eli Zaretskii
2016-02-29 18:55 ` Simon Marchi
2016-02-02 18:05 Doug Evans
2016-02-02  1:03 Doug Evans
2016-02-02 16:10 ` Eli Zaretskii
2016-02-04 13:47 ` Pedro Alves

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=001a1145617e604203052d191f01@google.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@ericsson.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).