From: David Knuth <dknuth@intellibot.cc>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb is breaking at wrong locations
Date: Wed, 02 Oct 2002 07:39:00 -0000 [thread overview]
Message-ID: <C9E682CA-D614-11D6-A87A-003065E3B32E@intellibot.cc> (raw)
In-Reply-To: <1020927215647.ZM25256@localhost.localdomain>
On Friday, September 27, 2002, at 05:56 PM, Kevin Buettner wrote:
>> 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?
I don't know. I inherited the system from engineers who are gone. So,
guess my next question is, does it make sense to go to a newer version
of GDB to try and fix this and if I do this, will I also have to
upgrade the gcc cross toolchain?
David
========================================================
David Knuth dknuth@intellibot.cc (804) 543-2703
prev parent reply other threads:[~2002-10-02 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:02 David Knuth
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 [this message]
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=C9E682CA-D614-11D6-A87A-003065E3B32E@intellibot.cc \
--to=dknuth@intellibot.cc \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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