From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Prepare Solaris x86 for 64-bit Solaris 10
Date: Sat, 30 Oct 2004 19:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0410301957000.4049@digraph.polyomino.org.uk> (raw)
In-Reply-To: <200410301950.i9UJorQL009142@elgar.sibelius.xs4all.nl>
On Sat, 30 Oct 2004, Mark Kettenis wrote:
> Including a .c file is perhaps a bit unorthodox, but this really is
> the most elegant way I can think of to solve the issue with the
> upcoming 64-bit Solaris 10.
I had considered such an approach but decided against it on the grounds of
lack of any precedent in GDB for one .c file to include another.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2004-10-30 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 19:51 Mark Kettenis
2004-10-30 19:59 ` Joseph S. Myers [this message]
2004-10-30 20:53 ` Andrew Cagney
2004-10-30 21:13 ` Mark Kettenis
2004-10-30 21:59 ` Andrew Cagney
2004-10-31 15:35 ` Mark Kettenis
2004-10-31 15:58 ` Andrew Cagney
2004-10-31 21:24 ` Joseph S. Myers
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=Pine.LNX.4.61.0410301957000.4049@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/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