From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>,
"Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: long long considered harmful?
Date: Thu, 24 Apr 2003 23:51:00 -0000 [thread overview]
Message-ID: <000901c30abd$766038a0$2a00a8c0@dash> (raw)
In-Reply-To: <3EA85183.9000106@redhat.com>
> I thought snow was one of Canada's two main exports?
Yeah, but in April? Ick.
> More seriously, a things-to-do-today item is to add to gdb (well
> immediatly remote.c) code that reads in a regformats file, and then uses
> that to unpack a raw target byte-ordered (or network ordered?) buffer.
>
> Kris, that problem sounds very similar to what you're doing here.
It is. We already handle it fairly well in our pdebug protocol but I think
what you're talking about would be very handy. We used to monkey around
with the data a lot more than I do now since gdb is pretty good at knowing
what the target is and dealing with the registers. I think the place where
it would be really useful for us is in marshalling and unmarshalling our
pdebug stuff. We could probably simplify a lot and remove some assumptions.
cheers,
Kris
prev parent reply other threads:[~2003-04-24 23:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 17:39 Kris Warkentin
2003-04-22 17:45 ` Daniel Jacobowitz
2003-04-22 18:08 ` Kris Warkentin
2003-04-22 18:21 ` Daniel Jacobowitz
2003-04-22 18:41 ` Kris Warkentin
2003-04-22 19:31 ` Daniel Jacobowitz
2003-04-22 19:12 ` Kris Warkentin
2003-04-22 19:25 ` Kris Warkentin
2003-04-22 19:30 ` Daniel Jacobowitz
2003-04-23 13:39 ` Kris Warkentin
2003-04-23 21:17 ` Daniel Jacobowitz
2003-04-23 21:23 ` Kris Warkentin
2003-04-23 21:44 ` Kris Warkentin
2003-04-23 21:47 ` Daniel Jacobowitz
2003-04-23 22:09 ` Kris Warkentin
2003-04-23 22:11 ` Daniel Jacobowitz
2003-04-23 22:17 ` Kris Warkentin
2003-04-24 21:05 ` Andrew Cagney
2003-04-24 23:51 ` 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='000901c30abd$766038a0$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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).