public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL
Date: Thu, 17 Dec 2015 15:14:00 -0000	[thread overview]
Message-ID: <4a6ed09b0f70c79b11bc1e0973a7333d9316a287@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 4a6ed09b0f70c79b11bc1e0973a7333d9316a287 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4a6ed09b0f70c79b11bc1e0973a7333d9316a287

Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL

Since we now rely on PTRACE_EVENT_CLONE being available (added in
Linux 2.5.46), we're relying on NPTL.

This commit removes the support for older LinuxThreads, as well as the
workarounds for vendor 2.4 kernels with NPTL backported.

 - Rely on tkill being available.

 - Assume gdb doesn't get cancel signals.

 - Remove code that checks the LinuxThreads restart and cancel signals
   in the inferior.

 - Assume that __WALL is available.

 - Assume that non-leader threads report WIFEXITED.

 - Thus, no longer need to send signal 0 to check whether threads are
   still alive.

 - Update comments throughout.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/ChangeLog:

	* configure.ac: Remove tkill checks.
	* configure, config.in: Regenerate.
	* linux-nat.c: Remove HAVE_TKILL_SYSCALL check.  Update top level
	comments.
	(linux_nat_post_attach_wait): Remove 'cloned' parameter.  Use
	__WALL.
	(attach_proc_task_lwp_callback): Don't set the cloned flag.
	(linux_nat_attach): Adjust.
	(kill_lwp): Remove HAVE_TKILL_SYSCALL check.  No longer fall back
	to 'kill'.
	(linux_handle_extended_wait): Use __WALL.  Don't set the cloned
	flag.
	(wait_lwp): Use __WALL.  Update comments.
	(running_callback, stop_and_resume_callback): Delete.
	(linux_nat_filter_event): Don't stop and resume all lwps. Don't
	check if the event LWP has previously exited.
	(check_zombie_leaders): Update comments.
	(linux_nat_wait_1): Use __WALL.
	(kill_wait_callback): Don't handle clone processes separately.
	Use __WALL instead.
	(linux_thread_alive): Delete.
	(linux_nat_thread_alive): Return true as long as the LWP is in the
	LWP list.
	(linux_nat_update_thread_list): Assume the kernel supports
	PTRACE_EVENT_CLONE.
	(get_signo): Delete.
	(lin_thread_get_thread_signals): Remove LinuxThreads references.
	No longer check __pthread_sig_restart / __pthread_sig_cancel in
	the inferior.
	* linux-nat.h (struct lwp_info) <cloned>: Delete field.
	* linux-thread-db.c: Update comments.
	(_initialize_thread_db): Remove LinuxThreads references.
	* nat/linux-waitpid.c (my_waitpid): No longer emulate __WALL.
	Pass down flags unmodified.
	* linux-waitpid.h (my_waitpid): Update documentation.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_kill_one_lwp): Remove references to
	LinuxThreads.
	(kill_lwp): Remove HAVE_TKILL_SYSCALL check.  No longer fall back
	to 'kill'.
	(linux_init_signals): Delete.
	(initialize_low): Adjust.
	* thread-db.c (thread_db_init): Remove LinuxThreads reference.


             reply	other threads:[~2015-12-17 15:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 15:14 sergiodj+buildbot [this message]
2015-12-17 15:11 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2015-12-18  0:11 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-12-18  0:28 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-18  3:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2015-12-18  3:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-12-18  3:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-18  3:41 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-12-18  3:41 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-12-18  3:52 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-12-18  3:53 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-12-18  5:10 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-12-18  8:45 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-12-19 14:05 ` Failures on Debian-i686, " sergiodj+buildbot
2015-12-19 14:31 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-12-19 14:49 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-12-20 13:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-12-20 13:34 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-21  6:24 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-21  6:45 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-12-21  7:05 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot

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=4a6ed09b0f70c79b11bc1e0973a7333d9316a287@gdb-build \
    --to=sergiodj+buildbot@redhat.com \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).