From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "Daniel Jacobowitz" <drow@mvista.com>, <gdb@sources.redhat.com>
Subject: Re: problem with exec-file when targetting remote machine
Date: Sun, 30 Mar 2003 01:12:00 -0000 [thread overview]
Message-ID: <000901c2f65a$1c8430b0$2a00a8c0@dash> (raw)
In-Reply-To: <3E8228B6.2030007@redhat.com>
> Assume the code was originally added because of a bug :-) I'm guessing
> something like:
>
> (gdb) file executable
> (gdb) disassemble main
>
> will break. It will select the wrong disassembler. Why isn't the
> executable being recognized, and why do the defaults fail? (NickC
> pointed me at an endian problem recently).
In case anyone is curious as to what the problem was, here it is.
I was suspicious about the $pc being incorrect even though it hit the
breakpoint at main. I stepped into our register stuffing code and observed
that everything was fine. As soon as I continued and checked the registers,
they were changed but only from $r15 onward (this is an sh4 target). I set
a watchpoint and it turns out that our floating point stuffing routine was
calculating the offset incorrectly and clobbering some of the gp registers.
The reason it was only happening with exec-file is that the default sh arch
wasn't retrieving fpregs and when it got a slightly different arch based on
the bfd, it would start asking for them and they'd get clobbered.
Cheers,
Kris
prev parent reply other threads:[~2003-03-30 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 20:07 Kris Warkentin
2003-03-24 20:36 ` Daniel Jacobowitz
2003-03-26 21:56 ` Kris Warkentin
2003-03-26 22:25 ` Andrew Cagney
2003-03-30 1:12 ` Kris Warkentin [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='000901c2f65a$1c8430b0$2a00a8c0@dash' \
--to=kewarken@qnx.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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