From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: mipsbe solib event breakpoint endian?
Date: Thu, 03 Jul 2003 14:59:00 -0000 [thread overview]
Message-ID: <008001c34173$d6d20b40$0202040a@catdog> (raw)
I'm having a problem with debugging on a mips big endian target. Mipsle
works fine but on mipsbe it looks like the solib-event breakpoint is
cross-endian. I don't have a target available right at this moment to show
you the exact output but it's trying to set the breakpoint at some freaking
huge number that doesn't look right at all. I'm assuming that it's reading
the memory from the target but not flipping it for some reason. Now
obviously this works for PowerPC so the functionality must be there.
Can anyone tell me if I'm barking up the wrong tree?
cheers,
Kris
next reply other threads:[~2003-07-03 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 14:59 Kris Warkentin [this message]
[not found] ` <1030708201312.ZM4704@localhost.localdomain>
2003-07-10 15:05 ` Kris Warkentin
2003-07-10 15:09 ` Daniel Jacobowitz
2003-07-10 15:15 ` Kevin Buettner
2003-07-10 15:33 ` Kris Warkentin
2003-07-10 17:05 ` Andrew Cagney
2003-07-10 17:16 ` Kris Warkentin
2003-07-10 18:42 ` Andrew Cagney
2003-07-10 19:14 ` Kris Warkentin
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='008001c34173$d6d20b40$0202040a@catdog' \
--to=kewarken@qnx.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