From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org, Luis Machado <lgustavo@codesourcery.com>
Subject: Re: [PATCH v2] PR threads/20743: Don't attempt to suspend or resume exited threads.
Date: Fri, 14 Apr 2017 22:40:00 -0000 [thread overview]
Message-ID: <6029590.iEtzOUCDnR@ralph.baldwin.cx> (raw)
In-Reply-To: <62fcaaa0-35e3-2bed-fb5e-336a5c5ffbf4@codesourcery.com>
On Wednesday, April 12, 2017 01:11:45 PM Luis Machado wrote:
> On 04/04/2017 12:32 PM, John Baldwin wrote:
> > When resuming a native FreeBSD process, ignore exited threads when
> > suspending/resuming individual threads prior to continuing the process.
> >
> > gdb/ChangeLog:
> >
> > PR threads/20743
> > * fbsd-nat.c (resume_one_thread_cb): Remove.
> > (resume_all_threads_cb): Remove.
> > (fbsd_resume): Use ALL_NON_EXITED_THREADS instead of
> > iterate_over_threads.
> ...
> > @@ -711,13 +679,37 @@ fbsd_resume (struct target_ops *ops,
> > if (ptid_lwp_p (ptid))
> > {
> > /* If ptid is a specific LWP, suspend all other LWPs in the process. */
> > - iterate_over_threads (resume_one_thread_cb, &ptid);
> > + struct thread_info *tp;
> > + int request;
> > +
> > + ALL_NON_EXITED_THREADS (tp)
> > + {
> > + if (ptid_get_pid (tp->ptid) != ptid_get_pid (ptid))
> > + continue;
> > +
> > + if (ptid_get_lwp (tp->ptid) == ptid_get_lwp (ptid))
> > + request = PT_RESUME;
> > + else
> > + request = PT_SUSPEND;
> > +
> > + if (ptrace (request, ptid_get_lwp (tp->ptid), NULL, 0) == -1)
> > + perror_with_name (("ptrace"));
> > + }
>
> Identation of the ALL_NON_EXITED_THREADS block is off. I'd check the
> identation of the entire block to make sure it is sane.
Hmm, the raw code looks fine. I know that my MUA (kmail) messes up formatting
of code as it displays tabs as 4 characters instead of 8? Here's the raw
code with tabs expanded to spaces:
ALL_NON_EXITED_THREADS (tp)
{
if (ptid_get_pid (tp->ptid) != ptid_get_pid (ptid))
continue;
if (ptid_get_lwp (tp->ptid) == ptid_get_lwp (ptid))
request = PT_RESUME;
else
request = PT_SUSPEND;
if (ptrace (request, ptid_get_lwp (tp->ptid), NULL, 0) == -1)
perror_with_name (("ptrace"));
}
> A question i have is why did we have to remove the original functions.
> Couldn't we have checked the non-exited-ness of the threads inside the
> callback?
That was what the V1 patch did, but you and Pedro requested it use
ALL_NON_EXITED_THREADS instead, hence version 2.
> Another bit... Since we're changing this code, might as well improve the
> perror message so it is more meaningful?
I could perhaps do a followup to include the ptrace op in the various
perror's in this file (all of them use this, as do the various BSD
nat.c files used for register fetch/store).
> Otherwise i have no further comments. I assume you ran gdb's testsuite
> against this change and verified the results are sane?
There were no regressions at least. With the stock tree there are
several unexpected failures already which I will get to at some point.
--
John Baldwin
next prev parent reply other threads:[~2017-04-14 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:33 John Baldwin
2017-04-11 18:43 ` John Baldwin
2017-04-12 18:12 ` Luis Machado
2017-04-14 22:40 ` John Baldwin [this message]
2017-04-15 1:01 ` Luis Machado
2017-04-17 18:27 ` John Baldwin
2017-04-17 18:32 ` Luis Machado
2017-04-18 14:27 ` Simon Marchi
2017-04-18 14:29 ` Simon Marchi
2017-04-18 14:58 ` Pedro Alves
2017-04-18 16:53 ` John Baldwin
2017-04-18 11:33 ` Pedro Alves
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=6029590.iEtzOUCDnR@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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