This is the mail archive of the
mailing list for the eCos project.
Chris Zimman wrote:
> [-- snip --]
> Quoting reams of previous message is also not required, just enough to
> of continue the conversation.
>> I did not have mincom running.
>> I type arm-eabi-gdb -nw
>> at the gdb prompt
>> set remotebaud 38400
>> target remote /dev/ttyS0
>> After this according to the ecos documentation I should see some
>> about the current loaction and language.
>> What I get is
>> Remote Debugging using /dev/ttyS0
>> 0x08003b3a in ?? ()
>> I dont get any extra information.
> It looks as though GDB has attached and you are sitting at the current PC.
>> Is this a problem?
> No, not necessarily. You may well be sitting in Redboot also, which GDB
> knows nothing about in terms of symbols (since you haven't told it about
> I don't mean this in any kind of an insulting way, but do you know how to
> GDB for something like this (eg. are you familiar with add-symbol-file)?
> Did you build the tests with debugging enabled (eg. -g)?
> Again, because there isn't really a ton of info here, I can't just look at
> and say "Ah ha! The problem is [whatever]"
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
I am not entirely familiar with gdb in these circumstances.
I have simply followed the examples give in the eCos documentation and am
trying to understand why things are not working.
This is why there is not a lot of information.
All tests were built using -g
Cannot download a file using mincom it will just sit there
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22912141.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss