>> 1) If I try to run the program from gdbserver (i.e. gdbserver /dev/ttyS0
>> wlsd), I get "readchar: Input/output error" messages,
>> and nothing works. See attached file gdb_fail.
>> What is going on here ?
>It sounds like your serial port is messed up.
What exactly do you mean by "messed up" ?
minicom seems to work OK. What do I need to check ?
>> 3) If I repeat the scenario described in 2), but with "set debug remote 1",
>> it seems to work somewhat faster
>> (e.g. bt takes about 1 minute to complete).
>> I am seeing alot of "Packet instead of Ack, ignoring it" messages.
>> See attached file gdb_trace_debug.
>> What do these messages mean ?
>Try "set debug serial 1" in addition - it's very verbose but maybe it
> will tell you what the "packet" is.
Running with "set debug serial 1" gives me the following:
In the gdb session,I see lots of the following messages:
[O][K][#][a][$]Packet instead of Ack, ignoring it
Simultaneously, in the gdbserver session (via minicom) I see:
Then, in the gdb session, I see lots of the following:
[c][c][#][$]Packet instead of Ack, ignoring it
at which point, the gdbserver (minicom) session now proudly shows:
See the attached file (gdb_trace_serial).
Why am I seeing stuff printed at the gdbserver (minicom) session ? Is this an
something is wrong with the serial port, and if so, what ? What is the
significance of the
messages gdb thinks are "Packet instead of Ack", which also seem to get printed
out (once) in the
gdbserver session ?