From: Jim Blandy <jimb@redhat.com>
To: rda@sources.redhat.com
Subject: PATCH: thread-db.c get_thread_signals doc fix
Date: Tue, 19 Oct 2004 22:50:00 -0000 [thread overview]
Message-ID: <vt2breyjpd6.fsf@zenia.home> (raw)
Committed as obvious.
2004-10-19 Jim Blandy <jimb@redhat.com>
* thread-db.c (get_thread_signals): Doc fix.
***************
*** 1205,1213 ****
}
/* Function: get_thread_signals
! Obtain the values of the "cancel", "restart" and "debug" signals
! used by linux threads, and store them in a set of global variables
! for use by check_child_state and friends. */
static int cancel_signal;
static int restart_signal;
--- 1342,1360 ----
}
/* Function: get_thread_signals
!
! Obtain the values of the "cancel", "restart" and "debug" signals
! used by LinuxThreads, and store them in a set of global variables
! for use by check_child_state and friends.
!
! Recent versions of NPTL don't define these symbols at all; you must
! use the libthread_db event functions instead (td_ta_event_addr,
! ...) to find out about thread creation, thread exits, and so on.
!
! Older versions of LinuxThreads provide both interfaces. To avoid
! changing RDA's behavior on any system it supports, we use the older
! signal-based interface if present, and use the event-based
! interface as a fall-back. */
static int cancel_signal;
static int restart_signal;
reply other threads:[~2004-10-19 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt2breyjpd6.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).