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

[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 1314 bytes --]

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

See my earlier message to Dave Korn.

 > >  > 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?

Well its only the stuff before I type "next" i.e. Emacs starting up and
lots of:

 ...
 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
 ...

 > 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.

Thats much earlier. I attach the full transcript below.

Maybe its too hard to debug over the Internet as I don't understand the
internals well enough. It doesn't seem to be causing a problem for anybody
else and I can get round it in the way I suggested in my first message.

I'll raise the matter again when I understand it better.

Thanks for looking at it,

Nick


[-- Attachment #2: gdb log --]
[-- Type: application/octet-stream, Size: 963 bytes --]

  reply	other threads:[~2005-01-21  2:47 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
2005-01-21  2:47             ` Nick Roberts [this message]
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=16880.27555.756855.225654@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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