From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: clean up logic in linux_child_wait
Date: Sat, 08 Dec 2001 10:14:00 -0000 [thread overview]
Message-ID: <npher14lz7.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of Fri, 7 Dec 2001 23:12:40 -0500
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?
next prev parent reply other threads:[~2001-12-08 18:14 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 [this message]
2001-12-08 10:28 ` Daniel Jacobowitz
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=npher14lz7.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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