From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: clean up logic in linux_child_wait
Date: Sat, 08 Dec 2001 10:28:00 -0000 [thread overview]
Message-ID: <20011208132652.A4190@nevyn.them.org> (raw)
In-Reply-To: <npher14lz7.fsf@zwingli.cygnus.com>
On Sat, Dec 08, 2001 at 01:15:24PM -0500, Jim Blandy wrote:
>
> Daniel Jacobowitz <drow@mvista.com> writes:
> > > GDB still uses linux-thread.c on the S/390.
> >
> > It shouldn't.
> >
> > >From the current sources I see:
> > NATDEPFILES= infptrace.o solib.o inftarg.o fork-child.o corelow.o s390-nat.o linux-thread.o core-aout.o core-regset.o
> > # post 5.0 natdepfiles.
> > NATDEPFILES+= thread-db.o lin-lwp.o proc-service.o
> >
> > i.e. it's actually using _both_. What dies horribly if you kill
> > linux-thread.o? That module is pretty severely deprecated.
>
>
> Well, the only thing that dies horribly is the three testsuite
> failures I was trying to resolve.
>
> Do you want my job?
Sorry for my tone there.
On Oct. 14, Mark Kettenis checked in a patch that was intended to make
all Linux targets use lin-lwp instead of linux-thread. The fact that
S/390 still was afterwards was probably just an oversight; S/390 now
contains the only reference to that file out of any port.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-08 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 20:05 Jim Blandy
2001-12-07 20:13 ` Daniel Jacobowitz
2001-12-08 10:14 ` Jim Blandy
2001-12-08 10:28 ` Daniel Jacobowitz [this message]
2001-12-08 19:46 ` Jim Blandy
2001-12-09 10:16 ` Andrew Cagney
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=20011208132652.A4190@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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