Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: John Baldwin <jhb@freebsd.org>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] PR threads/20743: Don't attempt to suspend or resume exited threads.
Date: Sat, 15 Apr 2017 01:01:00 -0000	[thread overview]
Message-ID: <b7414b1d-ff19-23f2-8f35-c1dd0b1395e0@codesourcery.com> (raw)
In-Reply-To: <6029590.iEtzOUCDnR@ralph.baldwin.cx>

On 04/14/2017 05:40 PM, John Baldwin wrote:
> 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:

Ah, that could very well be it.

>
>       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"));
>         }
>

The indentation here looks fine indeed.

>> 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.
>

Sorry, i swapped out the context of v1.

>> 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).
>

That sounds like a good idea and could be postponed to a more convenient 
time.

>> 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.
>

Great. I have no further comments.


  reply	other threads:[~2017-04-15  1:01 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
2017-04-15  1:01     ` Luis Machado [this message]
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=b7414b1d-ff19-23f2-8f35-c1dd0b1395e0@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.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