From: Mark Kettenis <kettenis@gnu.org>
To: gdb@sources.redhat.com
Subject: [RFC] HP-UX native support
Date: Sat, 16 Oct 2004 15:04:00 -0000 [thread overview]
Message-ID: <200410152226.i9FMQd8J001218@elgar.sibelius.xs4all.nl> (raw)
One of the black pages in GDB's history is what is usually referred to
as the HP merge. It's what brought us real support for modern HP-UX,
and included nifty features such as follow-fork and such.
Unfortunately the changes didn't fit in very well with the structure
of GDB in those days. We still suffer from the consequences.
Since then, the HP-UX specific code has seen very little maintenance,
and while I appreciate the efforts of Joel and Randolph to fix things,
I think some more radical changes are needed.
In my tree I have some changes that implement fresh new inf-ptrace.c
based native support for HP-UX 10.20. It does away with all the nifty
features mentioned above, and leaves us with something more
traditional. However, I think it'll make maintenance much easier, and
to be honest, I really doubt whether the nifty features still work.
How do people feel about this?
Mark
next reply other threads:[~2004-10-15 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 15:04 Mark Kettenis [this message]
2004-10-16 16:59 ` Michael Chastain
2004-10-16 17:46 ` Daniel Jacobowitz
2004-10-18 17:32 ` 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=200410152226.i9FMQd8J001218@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--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