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>, Kevin Buettner <kevinb at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 27 Sep 2002 14:56:47 -0700
- Subject: Re: gdb is breaking at wrong locations
- References: <0C60448A-D258-11D6-996B-003065E3B32E@intellibot.cc>
On Sep 27, 4:31pm, David Knuth wrote:
> On Friday, September 27, 2002, at 03:15 PM, Kevin Buettner wrote:
>
> > 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.
>
> I suspected this also, but I have only one set of sources, did a clean
> build, and had gdb load the ROM image. Incidentally, this is how I do
> it. If there is a better way, please enlighten me. (I'm doing this
> from memory, so the exact wording might be off.)
>
> > sudo modprobe bdm
> > cd src
> >m68k-unknown-coff-gdb
> $file ../bin/rom
> $target bdm /dev/icd_bdm0
> $r
> Download source from src/../bin/rom? (y or n) [y] y
>
> So, from the above, I don't know how the symbol file and executable
> could be mismatched because they are the same file, right?
That looks reasonable.
Has it *ever* worked correctly in the past?
Kevin