This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Friday, September 27, 2002, at 05:56 PM, Kevin Buettner wrote:
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?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?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |