From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: teawater@gmail.com, gdb@sourceware.org
Subject: Re: System call support in process record and replay
Date: Mon, 01 Jun 2009 15:09:00 -0000 [thread overview]
Message-ID: <E1MB98o-000812-I0@fencepost.gnu.org> (raw)
In-Reply-To: <200905311747.n4VHlY3b026655@brahms.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 31 May 2009 19:47:34 +0200 (CEST))
> Date: Sun, 31 May 2009 19:47:34 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: teawater@gmail.com, gdb@sourceware.org
>
> I think it is up to whoever adds support for an OS that doesn't use
> int 0x80 to come up with a more general solution.
That's me ;-) I intend to add support for DJGPP. Thus my questions
(and the numbers of interrupts hinted on that, btw).
So please consider sharing your thoughts about this.
TIA
next prev parent reply other threads:[~2009-06-01 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 10:11 Eli Zaretskii
2009-05-30 21:13 ` Doug Evans
2009-05-31 5:58 ` Hui Zhu
2009-05-31 17:47 ` Mark Kettenis
2009-06-01 15:09 ` Eli Zaretskii [this message]
2009-06-01 19:29 ` Michael Snyder
2009-06-01 7:14 ` Andi Kleen
2009-06-01 7:19 ` Hui Zhu
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=E1MB98o-000812-I0@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=teawater@gmail.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