public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yvan Roux <yvan.roux@linaro.org>
To: Pedro Alves <palves@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] Avoid deadlock in guality tests.
Date: Thu, 07 Apr 2016 13:41:00 -0000	[thread overview]
Message-ID: <CAD57uCe+dJODe7S8EgaZimMs+JCBGK1HfBqWgBnx-hZFJVw-1A@mail.gmail.com> (raw)
In-Reply-To: <CAD57uCc9U982atEUNgeT1Nx5X_5WCdviOuFqk8g0EFnuTNYrMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

Hi,

On 6 April 2016 at 17:29, Yvan Roux <yvan.roux@linaro.org> wrote:
> On 6 April 2016 at 17:24, Pedro Alves <palves@redhat.com> wrote:
>> On 04/06/2016 04:13 PM, Yvan Roux wrote:
>>> On 6 April 2016 at 17:09, Pedro Alves <palves@redhat.com> wrote:
>>>> On 04/06/2016 03:53 PM, Yvan Roux wrote:
>>>>> Dejagnu cleanup mechanism needs to be enhanced, but I think that it
>>>>> would also be better if guality tests don't get stuck and/or can be
>>>>> killed easily.  This patch changes GDB signals handling to nostop for
>>>>> SIGSEGV, SIGINT, SIGTERM and SIGBUS.  I am not sure if we need to
>>>>> increase the list of signals to all the stop ones (which are not used
>>>>> by GDB) or to restrict it just to SIGSEGV.
>>>>
>>>> I'd suggest:
>>>>
>>>>  handle all pass nostop
>>>>  handle SIGINT pass nostop
>>>>
>>>> That would make gdb pass _all_ signals except SIGTRAP
>>>
>>> I've committed it already :/
>>>
>>> I can make the change, but isn't there cases where SIGILL is used for
>>> breakpoints in GDB (I think I've seen that somewhere).
>>
>> True, and SIGSEGV and SIGEMT too.  But GDB handles that transparently
>> and won't pass such a breakpoint signal to the program, even with
>> "handle pass".  Only "handle SIGTRAP pass" passes a
>> breakpoint/step/etc. trap to the program.
>
> Ah ok, thanks for the explanations Pedro, I'll prepare a new patch and
> validate it.

Here is the new patch which makes GDB pass all signals except SIGTRAP.
validated on native armv8l target without regessions. ok for trunk ?

Cheers,
Yvan

2016-04-07  Yvan Roux  <yvan.roux@linaro.org>
            Pedro Alves  <palves@redhat.com>

        * gcc.dg/guality/guality.h (main): Make GDB pass all signals except
        SIGTRAP.

[-- Attachment #2: guality-fix.diff --]
[-- Type: text/plain, Size: 550 bytes --]

diff --git a/gcc/testsuite/gcc.dg/guality/guality.h b/gcc/testsuite/gcc.dg/guality/guality.h
index d5867d8..acf977f 100644
--- a/gcc/testsuite/gcc.dg/guality/guality.h
+++ b/gcc/testsuite/gcc.dg/guality/guality.h
@@ -252,10 +252,8 @@ main (int argc, char *argv[])
       if (!guality_gdb_input
 	  || fprintf (guality_gdb_input, "\
 set height 0\n\
+handle all pass nostop\n\
 handle SIGINT pass nostop\n\
-handle SIGTERM pass nostop\n\
-handle SIGSEGV pass nostop\n\
-handle SIGBUS pass nostop\n\
 attach %i\n\
 set guality_attached = 1\n\
 b %i\n\

  reply	other threads:[~2016-04-07 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 14:54 Yvan Roux
2016-04-06 15:01 ` Jakub Jelinek
2016-04-06 15:09 ` Pedro Alves
2016-04-06 15:13   ` Yvan Roux
2016-04-06 15:24     ` Pedro Alves
2016-04-06 15:29       ` Yvan Roux
2016-04-07 13:41         ` Yvan Roux [this message]
2016-04-07 23:46           ` 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=CAD57uCe+dJODe7S8EgaZimMs+JCBGK1HfBqWgBnx-hZFJVw-1A@mail.gmail.com \
    --to=yvan.roux@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).