From: Mark Kettenis <kettenis@gnu.org>
To: randolph@tausq.org
Cc: gdb@sources.redhat.com
Subject: Slimmed down HP-UX native code
Date: Sat, 11 Dec 2004 23:13:00 -0000 [thread overview]
Message-ID: <200412112313.iBBNDLeg008435@elgar.sibelius.xs4all.nl> (raw)
Still worried about having to maintain too much code ;-) ?
$ cat hppah-nat.c infttrace.c | wc -l
6996
$ cat hppa-hpux-nat.c inf-ttrace.c | wc -l
1212
To be honest, the new code doesn't do follow-exec/fork/vfork. But I
think I can implement that in less than 5000 lines of code ;-)
Mark
next reply other threads:[~2004-12-11 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 23:13 Mark Kettenis [this message]
2004-12-11 23:27 ` Randolph Chung
2004-12-12 4:45 ` Eli Zaretskii
2004-12-12 15:58 ` Mark Kettenis
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=200412112313.iBBNDLeg008435@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.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