From: Simon Marchi <simon.marchi@polymtl.ca>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 5/7] Add thread_db_notice_clone to gdbserver
Date: Sat, 06 May 2017 01:46:00 -0000 [thread overview]
Message-ID: <06e2d2b6c1aa9f0f9a151caf7db22356@polymtl.ca> (raw)
In-Reply-To: <20170408230727.0f65ad8f@pinnacle.lan>
On 2017-04-09 02:07, Kevin Buettner wrote:
> While working on a patch for fetching a thread handle in gdbserver, I
> ran into a circumstance in which tests in gdb.mi/mi-nsmoribund.exp
> would occasionally fail. Over a large enough number of runs, it would
> fail roughly 2% of the time.
>
> That thread handle patch caused find_one_thread() to be called on
> every stop. find_one_thread() calls td_ta_map_lwp2thr() which, in
> turn, can cause ps_get_thread_area() to be called.
> ps_get_thread_area() makes a call to ptrace() for getting the thread
> area address. If this should happen when the thread is not stopped,
> the call to ptrace will return error which in turn propogates back to
> find_one_thread(). find_one_thread() calls error() in this instance
> which causes the program to die.
>
> This patch causes find_one_thread() to be called upon reciept of a
> clone event. Since the clone is stopped, the circumstances described
> above cannot occur.
This patch looks good to me, although I'm not very knowledgeable in the
thread handling area.
Just one comment below.
> diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
> index e27cbf8..6f06eb8 100644
> --- a/gdb/gdbserver/linux-low.c
> +++ b/gdb/gdbserver/linux-low.c
> @@ -653,6 +653,8 @@ handle_extended_wait (struct lwp_info
> **orig_event_lwp, int wstat)
> new_lwp->status_pending = status;
> }
>
> + thread_db_notice_clone (get_thread_process (event_thr), ptid);
> +
> /* Don't report the event. */
> return 1;
> }
> diff --git a/gdb/gdbserver/linux-low.h b/gdb/gdbserver/linux-low.h
> index 7dcbfcf..87ce53a 100644
> --- a/gdb/gdbserver/linux-low.h
> +++ b/gdb/gdbserver/linux-low.h
> @@ -409,5 +409,6 @@ int thread_db_handle_monitor_command (char *);
> int thread_db_get_tls_address (struct thread_info *thread, CORE_ADDR
> offset,
> CORE_ADDR load_module, CORE_ADDR *address);
> int thread_db_look_up_one_symbol (const char *name, CORE_ADDR *addrp);
> +void thread_db_notice_clone (struct process_info *proc, ptid_t lwp);
Could you add a comment to document this function?
Thanks,
Simon
next prev parent reply other threads:[~2017-05-06 1:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 5:50 [PATCH v2 0/7] Thread handle to thread info mapping Kevin Buettner
2017-04-09 6:06 ` [PATCH v2 1/7] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2017-05-05 3:26 ` Simon Marchi
2017-07-19 0:01 ` Kevin Buettner
2017-04-09 6:07 ` [PATCH v2 2/7] Add `thread_from_thread_handle' function to (Python) gdb module Kevin Buettner
2017-04-13 16:11 ` Phil Muldoon
2017-05-05 3:54 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 4/7] Test case for gdb.thread_from_thread_handle Kevin Buettner
2017-05-05 5:19 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 7/7] Documentation for qXfer:threads:read handle attribute Kevin Buettner
2017-04-09 8:09 ` Eli Zaretskii
2017-04-09 6:07 ` [PATCH v2 3/7] Documentation for gdb.thread_from_thread_handle Kevin Buettner
2017-05-05 4:01 ` Simon Marchi
2017-05-05 6:25 ` Eli Zaretskii
2017-07-19 0:13 ` Kevin Buettner
2017-04-09 6:07 ` [PATCH v2 6/7] Add thread_handle_to_thread_info support for remote targets Kevin Buettner
2017-05-06 2:28 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 5/7] Add thread_db_notice_clone to gdbserver Kevin Buettner
2017-05-06 1:46 ` Simon Marchi [this message]
2017-04-20 0:19 ` [PATCH v2 0/7] Thread handle to thread info mapping Kevin Buettner
2017-04-26 17:46 ` Kevin Buettner
2017-05-03 18:32 ` Kevin Buettner
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=06e2d2b6c1aa9f0f9a151caf7db22356@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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