public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: kevinb@sourceware.org To: src-cvs@sourceware.org Subject: src/rda/unix ChangeLog lwp-pool.c lwp-pool.h t ... Date: Thu, 14 Jun 2012 20:21:00 -0000 [thread overview] Message-ID: <20120614202158.24886.qmail@sourceware.org> (raw) CVSROOT: /cvs/src Module name: src Changes by: kevinb@sourceware.org 2012-06-14 20:21:58 Modified files: rda/unix : ChangeLog lwp-pool.c lwp-pool.h thread-db.c Log message: * lwp-pool.c (struct lwp): Add new field `disabled'. (empty_lwp_slot): New static global. (hash_empty_slot, resize_hash, lwp_pool_stop_all) (lwp_pool_continue_all, clear_all_do_step_flags) (hash_find): Rename to hash_find_1. Add parameter `create_p'. Initialize `disabled' field. (hash_find, hash_find_no_create, lwp_pool_disable_lwp) (lwp_pool_enable_lwp): New functions. (hash_delete): Revise method used for deleting a slot from the hash table. (lwp_pool_continue_all): Don't continue disabled LWPs. (lwp_pool_continue_lwp): Print a warning instead of an error, and then only when LWP Pool diagnostics are enabled when attempting to continue a LWP with the state of lwp_state_stopped_stop_pending_interesting. * lwp-pool.h (lwp_pool_disable_lwp, lwp_pool_enable_lwp): Declare. * thread-db.c (find_new_threads_callback): Adjust thread deletion / reuse message. (update_thread_list): Disable continuation of zombie threads. (thread_db_break_program): Enable diagnostic message for "monitor thread-db-noisy". Use kill_lwp() instead of kill(). (thread_db_check_child_state): Don't stop on signals from zombie threads. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/ChangeLog.diff?cvsroot=src&r1=1.67&r2=1.68 http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/lwp-pool.c.diff?cvsroot=src&r1=1.7&r2=1.8 http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/lwp-pool.h.diff?cvsroot=src&r1=1.3&r2=1.4 http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/thread-db.c.diff?cvsroot=src&r1=1.21&r2=1.22
next reply other threads:[~2012-06-14 20:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-14 20:21 kevinb [this message] -- strict thread matches above, loose matches on Subject: below -- 2004-12-03 21:36 jimb 2004-11-29 19:36 jimb
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=20120614202158.24886.qmail@sourceware.org \ --to=kevinb@sourceware.org \ --cc=src-cvs@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: linkBe 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).