From: Chris Gniady <gniady@ecn.purdue.edu>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: gdbserver on ixp1200
Date: Sun, 08 Dec 2002 02:47:00 -0000 [thread overview]
Message-ID: <3DF3235F.7080204@ecn.purdue.edu> (raw)
In-Reply-To: <3DF32223.3090306@ecn.purdue.edu>
Daniel,
That was it. Thank you!!!!!
Once I saw your patch for the big endian, I realized the problem. I have
seen the breakpoint instruction mentioned on other sites, but did not
cross my mind to look that it may be in little endian order.
Thanks again,
Chris
prev parent reply other threads:[~2002-12-08 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1039308677.1853.ezmlm@sources.redhat.com>
2002-12-07 17:28 ` Chris Gniady
2002-12-07 17:33 ` Daniel Jacobowitz
2002-12-07 20:18 ` Daniel Jacobowitz
[not found] ` <3DF32223.3090306@ecn.purdue.edu>
2002-12-08 2:47 ` Chris Gniady [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=3DF3235F.7080204@ecn.purdue.edu \
--to=gniady@ecn.purdue.edu \
--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