public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Set process affinity in test to work around ARM ptrace bug
Date: Fri, 02 Sep 2016 01:00:00 -0000	[thread overview]
Message-ID: <c7958447-e3ea-a130-12c7-a558abcbfff3@redhat.com> (raw)
In-Reply-To: <86vayfbrrf.fsf@gmail.com>

On 09/01/2016 03:48 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
> 
>> But since this is only for when running the testsuite alone, I could argue that
>> this masks the problem and thus makes it look like gdb works better on an
>> affected system than it really does.  I think if I were working on gdb/gdbserver
>> on arm, I'd much prefer if gdb told me my system had a broken ptrace, so I
>> could act on it, rather than masking it off and pretend all is well.
>> How about we make gdb / gdbserver detect bad kernel version, and output a
>> warning to the effect?  We already have precedent in
>> nat/linux-ptrace.c.
> 
> Do you mean linux_ptrace_test_ret_to_nx_instr?

Yes.

> 
>> I think we should probably do that regardless of any testsuite workaround.
>>
> 
> Yes, I agree.  I'll write a test in nat/linux-ptrace.c too.
> 

> I happen to see there is a proc gdb_skip_float_test, so I write a patch
> to detect broken kernel ptrace in it, and use gdb_skip_float_test all
> over the test cases.  How about the patch below?

I like it.  This version LGTM.  Thanks for adjusting.

-- 
Pedro Alves

  reply	other threads:[~2016-09-02  1:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 13:57 Yao Qi
2016-06-30 14:20 ` Antoine Tremblay
2016-06-30 15:32 ` Pedro Alves
2016-07-04 10:50   ` Yao Qi
2016-07-25 13:22     ` Yao Qi
2016-07-25 14:28       ` Pedro Alves
2016-09-01 14:48         ` Yao Qi
2016-09-02  1:00           ` Pedro Alves [this message]
2016-09-02  8:24             ` Yao Qi

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=c7958447-e3ea-a130-12c7-a558abcbfff3@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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).