Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] test hand function call in commands list
Date: Wed, 23 Apr 2003 00:50:00 -0000	[thread overview]
Message-ID: <20030423005039.GJ2402@gnat.com> (raw)
In-Reply-To: <20030416142321.GA7612@nevyn.them.org>

> 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.
> 
> Did this ever work?  It looks like the call to error() when we stop in
> call_function_by_hand drops us out in start_event_loop, but the call to
> bpstat_do_actions is in command_handler (closer to the innermost end of
> the call chain, and thus bypassed by the error()).
> 
> Should we be calling bpstat_do_actions before that error()?

I had a quick look: This ``feature'' is present since at least 5.1.1
(I tried on Linux with 5.1.1, 5.2.1 and 5.3 - could not try with 5.0
as it had a problem reading DWARF2_FORM_strp). I don't know how Klee
got it to work.

Here is what I suggest: This issue is orthogonal to what we are trying
to test, so let's write a new test for it that does not rely on inferior
function calls to hit the breakpoints. We can also discuss whether we
consider this feature to be a bug or not.

What do you think?
-- 
Joel


  parent reply	other threads:[~2003-04-23  0:50 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
2003-04-23  0:50   ` Joel Brobecker [this message]
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=20030423005039.GJ2402@gnat.com \
    --to=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