From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: long long considered harmful?
Date: Wed, 23 Apr 2003 22:17:00 -0000 [thread overview]
Message-ID: <002b01c309e6$21eb4260$0202040a@catdog> (raw)
In-Reply-To: <20030423221137.GA6244@nevyn.them.org>
> At that point, the entire contents of this header (for GDB's purposes)
> could be:
> typedef union _debug_gregs
> {
> qnx_reg64 padding[1024];
> };
>
> Right?
>
> If so, honestly I don't see the point of including it in GDB at all.
You're absolutely right. Ultimately, if someone really wants to see how our
registers work, they can always go look at our system headers right?.
That's the problem with legacy code. It's not always easy to see the wheat
for the chaff. I think I'll get rid of all the register structures just as
you suggested.
cheers,
Kris
next prev parent reply other threads:[~2003-04-23 22:17 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 [this message]
2003-04-24 21:05 ` Andrew Cagney
2003-04-24 23:51 ` 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='002b01c309e6$21eb4260$0202040a@catdog' \
--to=kewarken@qnx.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