Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: internal-error: insert_step_resume_breakpoint_at_sal
Date: Thu, 20 Jan 2005 17:07:00 -0000	[thread overview]
Message-ID: <41EFE531.9060605@gnu.org> (raw)
In-Reply-To: <16879.224.997596.521183@farnswood.snap.net.nz>

Nick Roberts wrote:
>  > > Well symtab = 0x0 looks unassigned to me.
>  > 
>  > More likely not-found, what's at that address?
> 
> Whats at 0x0?! Are you winding me up, or is it some kind of offset?

What's at $pc (where PC is 0x4012e7e9 or 0x80850d5), symtab==0 indicates 
a symtab lookup failure.

>  > Can you capture the output from "set debug infrun 1"?  It should help.
> 
> See below. I can send the full transcript if necessary.

How much more?

> Nick
> 
> ...
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> 
> infrun: prepare_to_wait
> Breakpoint 3, Fsplit_window (window=137726961, size=137726961, 
>     horflag=137726961) at window.c:3688
> 3688      if (NILP (window))
> (gdb) n

There appears to be stuff missing here, the output should contain 
something like:

	resume(step=1, signal=0)
	resume(step=0, signal=0)

as GDB single-steps the thread off breakpoint 3.  The PC should be near 
or at 0x80850d5 found in the below.

> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x80850d5
> infrun: BPSTATE_WHAT_STOP_NOISY
> infrun: stop_stepping
> 
> Breakpoint 1, internal_error (file=0x82214d7 "infrun.c", line=2671, 
>     string=0x81ef681 "%s: Assertion `%s' failed.") at utils.c:789
> 789       va_start (ap, string);
> 

Andrew


  parent reply	other threads:[~2005-01-20 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  4:02 Nick Roberts
2005-01-16 10:54 ` Nick Roberts
2005-01-18 18:59   ` Andrew Cagney
2005-01-18 21:53     ` Nick Roberts
2005-01-19 15:55       ` Andrew Cagney
2005-01-20  0:59         ` Nick Roberts
2005-01-20 10:23           ` Dave Korn
2005-01-20 10:58             ` Nick Roberts
2005-01-20 17:07           ` Andrew Cagney [this message]
2005-01-21  2:47             ` Nick Roberts
2005-01-24 21:59               ` Andrew Cagney
2005-01-26 10:19                 ` Nick Roberts
2005-01-26 16:26                   ` Andrew Cagney
2005-01-26 20:48                     ` Nick Roberts
2005-01-26 21:39                       ` Andrew Cagney
2005-01-27  1:02                         ` Nick Roberts
2005-02-06  7:16                           ` Andrew Cagney
2005-02-06  7:26                             ` Andrew Cagney
2005-02-06 20:11                             ` Nick Roberts
2005-02-08 16:57                               ` Andrew Cagney

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=41EFE531.9060605@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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