Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] test hand function call in commands list
Date: Thu, 17 Apr 2003 02:40:00 -0000	[thread overview]
Message-ID: <20030417024002.GA10172@nevyn.them.org> (raw)
In-Reply-To: <20030416230905.GH1241@gnat.com>

On Wed, Apr 16, 2003 at 07:09:05PM -0400, Joel Brobecker wrote:
> > No; let's figure out what the new problem is first.  After that let's
> > get the test in as quickly as possible so that we know if it breaks
> > again :)
> 
> Sure.
> 
> > I can reproduce this.  It's even simpler; we aren't executing the
> > commands list even if if there's no inferior function call in them. 
> > This appears to be specific to commands on a breakpoint hit during an
> > inferior function call.
> 
> This is really bizarre. I do remember very clearly that removing the
> "silent" command in the commands list caused the breakpoint number to
> be printed. So it seemed that the commands where executed...

Silent is handled separately from the rest of the commands list; it's
handled when the breakpoint is hit, but the commands themselves run
later.

> > Did this ever work?
> 
> Since Klee posted the patch, I was assuming that he had it working at
> some point.

I don't know if it was tested in the FSF tree.  Although yes is
probably a safe bet...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-04-17  2:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 15:40 Joel Brobecker
2003-04-16 14:23 ` Daniel Jacobowitz
2003-04-16 23:09   ` Joel Brobecker
2003-04-17  2:40     ` Daniel Jacobowitz [this message]
2003-04-23  0:50   ` Joel Brobecker
2003-04-23  2:42   ` Michael Snyder
2003-06-29 20:11 ` Daniel Jacobowitz

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=20030417024002.GA10172@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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