>> Simultaneously, in the gdbserver session (via minicom) I see:
>> +$OK#9a
>Um.... you're running with a serial port open on the same port you're
>trying to debug on? That can't work. Use one for console and the
>other for gdbserver, or come to some other arrangement if your board
>only has one.
OK, thanks. I now have this sorted out. It seems the only way it agrees to work
is if I start gdbserver in a minicom session, and then kill -9 the minicom session, and then connect
with gdb.
So, now I have basic (command line) gdb <-> gdbserver working OK over the serial connection.
However, I am trying to run gdb from a GUI front end, which is running gdb/mi.
What I am seeing is that the GUI is invoking gdb/mi stack-info-depth, which seems to be
causing a memory exception in frame_register_unwind ("Cannot access memory at address 0x2c").
Thus, even though gdb is able to decipher the stack, the error at the end of the backtrace causes
the gdb/mi GUI to choke.
How can I work around this ?
Thanks !!
