Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <cagney@gnu.org>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed.
Date: Sun, 31 Oct 2004 16:18:00 -0000	[thread overview]
Message-ID: <jehdocktig.fsf@sykes.suse.de> (raw)
In-Reply-To: <41839D0D.8070700@gnu.org> (Andrew Cagney's message of "Sat, 30 Oct 2004 09:54:21 -0400")

Andrew Cagney <cagney@gnu.org> writes:

> The "step on breakpoint; ..." tests,

I can't find any such test in gdb.base.

> based on your description, exercise just that senario.  They run to a
> breakpoint, wait for a signal to be come pending, and then try to step
> et.al.
>
> Sounds like more is going on?

Perhaps the key point is that the signal (SIGIO) is silently passed to the
inferiour by gdb.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2004-10-30 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 19:32 Andreas Schwab
2004-10-30 14:54 ` Andrew Cagney
2004-10-30 17:47   ` Andreas Schwab
2004-10-30 19:48     ` Andrew Cagney
2004-10-31 16:18       ` Andreas Schwab [this message]
2004-10-31 19:12         ` Andrew Cagney
     [not found]           ` <je8y9okn2b.fsf@sykes.suse.de>
2004-11-01 18:05             ` Andrew Cagney
2004-11-02 15:25               ` Andreas Schwab
2005-01-26 21:10                 ` Andrew Cagney
2005-01-27 15:25                   ` Andreas Schwab
2004-10-30 17:27 ` infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed dot Mark Kettenis

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=jehdocktig.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=ac131313@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb@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