From: Sterling Augustine <saugustine@google.com>
To: Orlando Arias <oarias@knights.ucf.edu>
Cc: gdb@sourceware.org
Subject: Re: Issues debugging remote leon3 system
Date: Fri, 16 Jan 2015 16:38:00 -0000 [thread overview]
Message-ID: <CAEG7qUxHWnoVPxeva=mNngdR9RCVOCc__7U+akMW4jx86TPr8w@mail.gmail.com> (raw)
In-Reply-To: <54B9326B.8040804@knights.ucf.edu>
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.
prev parent reply other threads:[~2015-01-16 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 16:20 Orlando Arias
2015-01-15 20:39 ` Orlando Arias
2015-01-16 15:44 ` Orlando Arias
2015-01-16 16:38 ` Sterling Augustine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEG7qUxHWnoVPxeva=mNngdR9RCVOCc__7U+akMW4jx86TPr8w@mail.gmail.com' \
--to=saugustine@google.com \
--cc=gdb@sourceware.org \
--cc=oarias@knights.ucf.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox