Issues debugging remote leon3 system

Sterling Augustine saugustine@google.com
Fri Jan 16 16:38:00 GMT 2015


On Fri, Jan 16, 2015 at 7:46 AM, Orlando Arias <oarias@knights.ucf.edu> wrote:
> Greetings,
>
> Further providing information, I have found the following whilst
> debugging the issue:
>
> At some point, gdbserver sends the following string:
> $T050e:0*,;1e:0*"00ef90f6a0;50:0*,;51:0*,;0f:0*,;thread:p37b.37b;core:0;#54
>
> and gdb attempts to process:
> T050e:0000000000000000;1e:0008a6a000080e14;50:0000000000000000;51:0000000000000000;0f:0000000000000000;thread:p37e.37e;core:0;
>
> At the moment, I am not sure as to what I am looking at. I will continue
> working on finding the root cause. If anybody has any ideas, please let
> me know. Thank you.
>
> Cheers,
> Orlando.

Since no one is giving you anything to work with.

I know nothing about this processor or your architecture, or how it
interacts with gdb, but sometimes this type of problem occurs when gdb
and gdbserver disagree on the number of registers or their size of
registers at the target.

There can be many different sources of the problem, from mismatched
gdb versions to poorly written gdb stubs, to miscompiled programs.

Don't know if that will help, but that is where I would look.



More information about the Gdb mailing list