This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb is breaking at wrong locations
- From: Kevin Buettner <kevinb at redhat dot com>
- To: David Knuth <dknuth at intellibot dot cc>, gdb at sources dot redhat dot com
- Date: Fri, 27 Sep 2002 12:15:40 -0700
- Subject: Re: gdb is breaking at wrong locations
- References: <A32CA66C-D24B-11D6-996B-003065E3B32E@intellibot.cc>
On Sep 27, 3:02pm, David Knuth wrote:
> 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.
It sounds to me like you have a mismatch between the executable that
you're running on the target and the symbol file that you're loading
into gdb.
Kevin