From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dave@hiauly1.hia.nrc.ca
Cc: drow@false.org, gdb@sourceware.org, dave.anglin@nrc-cnrc.gc.ca,
brobecker@adacore.com
Subject: Re: Likely obsolete pieces of GDB
Date: Mon, 01 Jan 2007 17:10:00 -0000 [thread overview]
Message-ID: <200701011709.l01H9W6e009442@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200701011646.l01GkoxX026700@hiauly1.hia.nrc.ca> (dave@hiauly1.hia.nrc.ca)
> Date: Mon, 1 Jan 2007 11:46:49 -0500 (EST)
> From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>
> > > Tried a simple test with this version. Tried to debug gdb itself.
> > > Set a break on main and ran gdb with "-v". The exterior gdb dumped
> > > core. The cause seems to be that the deprecated_child_ops struct
> > > hasn't been initialized. It looks like the stuff in inf-ptrace.c
> > > needs to be merged into hpux-thread.c, or we need to setup
> > > deprecated_child_ops. Presumably, this was done at some point in
> > > the past.
> >
> > Is this worth fixing? Obviously no one has used it lately.
>
> Don't know but I probably would use it if it worked. I hacked
> on this a bit a couple of weeks ago. I mainly pulled code from
> inftarg.c with a bit of specialization for hpux. It builds and
> some stuff may work...
Hi Dave,
I'm sorry to say this, but I think you're on the wrong track. Instead
of replicating bits from the obsolete inftarg.c, this should really be
implemented as a threads stratum, much in the same way as
bsd-uthread.c.
I'll see if I can hack something up for you along those lines.
Unfortunately the HP-UX 10.20 system that I have access to, doesn't
have the threads stuff installed, so I can't test things.
Mark
next prev parent reply other threads:[~2007-01-01 17:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42 ` Pedro Alves
2007-02-10 23:50 ` Daniel Jacobowitz
2007-02-19 1:25 ` Pedro Alves
2006-12-17 1:24 ` John David Anglin
2006-12-17 11:46 ` Mark Kettenis
2007-01-01 16:34 ` Daniel Jacobowitz
2006-12-18 3:03 ` John David Anglin
2006-12-18 3:43 ` John David Anglin
2006-12-20 16:07 ` John David Anglin
2006-12-20 17:41 ` John David Anglin
2007-01-01 16:33 ` Daniel Jacobowitz
2007-01-01 16:47 ` John David Anglin
2007-01-01 17:10 ` Mark Kettenis [this message]
2007-01-01 17:20 ` John David Anglin
2006-12-17 1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26 ` Stephen & Linda Smith
2006-12-17 15:37 ` Daniel Jacobowitz
2006-12-20 6:01 ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58 ` Mark Kettenis
2007-01-03 23:55 ` Jim Blandy
2007-02-10 20:50 ` Daniel Jacobowitz
2007-02-12 17:35 ` Joel Brobecker
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=200701011709.l01H9W6e009442@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=drow@false.org \
--cc=gdb@sourceware.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