Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Increase timeout on gdb.base/exitsignal.exp
Date: Tue, 25 Aug 2015 18:31:00 -0000	[thread overview]
Message-ID: <55DCB471.4020103@redhat.com> (raw)
In-Reply-To: <87si77gr9x.fsf@redhat.com>

On 08/25/2015 07:24 PM, Sergio Durigan Junior wrote:

>> This (many instances) doesn't make sense to me.  And I think wouldn't
>> fix anything.  Seems to me the bumped timeout, if any, should be around
>> the continue that caused the first time out:
>>
>> # Continue until the end.
>> gdb_test "continue" "Program terminated with signal SIGSEGV.*" \
>>     "program terminated with SIGSEGV"
> 
> Sorry, I am confused...  The timeout does not occur on this command: it
> occurs on the print commands.  So I think we must extend the timeout for
> the print commands; don't we?

Not AFAICS from what you pasted.  The print time outs seem to me to be
cascading fails.  Highlighting what you pasted:

  (gdb) PASS: gdb.base/exitsignal.exp: $_exitcode is void before running
  continue
  Continuing.

  Program received signal SIGSEGV, Segmentation fault.
  0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6
  (gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV
  continue
  Continuing.
  FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  print $_exitsignal
  FAIL: gdb.base/exitsignal.exp: $_exitsignal is 11 (SIGSEGV) after SIGSEGV. (timeout)
  print $_exitcode
  FAIL: gdb.base/exitsignal.exp: $_exitcode is still void after SIGSEGV (timeout)
  kill

  Program terminated with signal SIGSEGV, Segmentation fault.
  The program no longer exists.
  (gdb) print $_exitsignal
  $3 = 11
  (gdb) print $_exitcode
  $4 = void

That timed out waiting for the "Program terminated with signal SIGSEGV"
output.  Stripping the prints, we see it more clearly:

  Program received signal SIGSEGV, Segmentation fault.
  0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6
  (gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV
  continue
  Continuing.
  FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout)
  Program terminated with signal SIGSEGV, Segmentation fault.
  The program no longer exists.
  (gdb)

Thanks,
Pedro Alves


  reply	other threads:[~2015-08-25 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  5:42 Sergio Durigan Junior
2015-08-25 10:43 ` Pedro Alves
2015-08-25 18:24   ` Sergio Durigan Junior
2015-08-25 18:31     ` Pedro Alves [this message]
2015-08-25 18:35       ` Sergio Durigan Junior
2015-08-25 18:45         ` Pedro Alves
2015-08-25 19:09           ` Peter Schauer
2015-08-25 19:13             ` Sergio Durigan Junior

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=55DCB471.4020103@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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