Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Knuth <dknuth@intellibot.cc>
To: gdb@sources.redhat.com
Subject: gdb is breaking at wrong locations
Date: Fri, 27 Sep 2002 12:02:00 -0000	[thread overview]
Message-ID: <A32CA66C-D24B-11D6-996B-003065E3B32E@intellibot.cc> (raw)

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Hi,

We've got an m68k-coff tool chain to develop for and debug a 68332 
board via BDM.  I'm using gdb 4.17 and an ICD BDM pod.  Today, I 
noticed that it is not stopping at the set break points.  It is 
stopping about 6 lines after it should, thus it is stopping at times 
when I don't expect it to.  All the break points are at lines the are 
the else of an if condition and all are a return error; statement.  
Also, gdb is crashing frequently, or at least it's telling me there's a 
SIGBUS fault and it cannot proceed.

1) Are there somethings I should look out for when setting break 
points?  Any no-nos?

2) Can I/ should I upgrade to a later version of GDB?  Will a newer 
version work with the older gcc/as/ld/ar tools I'm using now?

As a side note, I've noticed that if I remove the parallel port 
extension cable between the laptop and BDM pod, the number of crashes 
decreases.  The problem with not breaking at the right location does 
not go away, however.

David

========================================================
David Knuth     dknuth@intellibot.cc     (804) 543-2703

[-- Attachment #2: Type: text/enriched, Size: 1128 bytes --]

Hi,


We've got an m68k-coff tool chain to develop for and debug a 68332
board via BDM.  I'm using gdb 4.17 and an ICD BDM pod.  Today, I
noticed that it is not stopping at the set break points.  It is
stopping about 6 lines after it should, thus it is stopping at times
when I don't expect it to.  All the break points are at lines the are
the <bold>else</bold> of an <bold>if</bold> condition and all are a
<bold>return error; </bold>statement.  Also, gdb is crashing
frequently, or at least it's telling me there's a SIGBUS fault and it
cannot proceed.


1) Are there somethings I should look out for when setting break
points?  Any no-nos?  


2) Can I/ should I upgrade to a later version of GDB?  Will a newer
version work with the older gcc/as/ld/ar tools I'm using now?


As a side note, I've noticed that if I remove the parallel port
extension cable between the laptop and BDM pod, the number of crashes
decreases.  The problem with not breaking at the right location does
not go away, however.


David


========================================================

David Knuth     dknuth@intellibot.cc     (804) 543-2703

             reply	other threads:[~2002-09-27 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 12:02 David Knuth [this message]
2002-09-27 12:15 ` Kevin Buettner
2002-09-27 13:31   ` David Knuth
2002-09-27 14:56     ` Kevin Buettner
2002-10-02  7:39       ` David Knuth

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=A32CA66C-D24B-11D6-996B-003065E3B32E@intellibot.cc \
    --to=dknuth@intellibot.cc \
    --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