From: Joel Brobecker <brobecker@gnat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Question regarding i386v4-nat.c:supply_gregset and fill_gregset
Date: Tue, 13 Aug 2002 15:53:00 -0000 [thread overview]
Message-ID: <20020813225259.GJ916@gnat.com> (raw)
In-Reply-To: <200208132206.g7DM6IOV034806@elgar.kettenis.dyndns.org>
> Sorry for the slow response. I was having a vacation :-).
Actually, me too :-).
> That would be a valid approach (although I would name the functions
> i386_supply_gregs and i386_fill_gregs). On the other hand, I wouldn't
> object to duplicating the small bits of code for Interix and deal with
> it later. I'll have to rethink these functions sooner or later if I
> want to support cross-debugging of core files.
This is the route I took: duplicating this small bit of code, leaving
the cleanup for later.
--
Joel
prev parent reply other threads:[~2002-08-13 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 18:04 Joel Brobecker
2002-08-07 6:16 ` Daniel Jacobowitz
2002-08-13 15:06 ` Mark Kettenis
2002-08-13 15:53 ` Joel Brobecker [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=20020813225259.GJ916@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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