Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wei-min Pan <weimin.pan@oracle.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.base/siginfo-thread.exp: Increase timeout for 'gcore' command
Date: Thu, 16 Mar 2017 16:00:00 -0000	[thread overview]
Message-ID: <58CAB698.7040602@oracle.com> (raw)
In-Reply-To: <868to5mgam.fsf@gmail.com>

Yao Qi wrote:
> Weimin Pan <weimin.pan@oracle.com> writes:
>
>   
>> The following failed lines from running test case siginfo-thread:
>>
>> FAIL: gdb.base/siginfo-thread.exp: save a core file (timeout)
>> FAIL: gdb.base/siginfo-thread.exp: extract si_addr
>> FAIL: gdb.base/siginfo-thread.exp: p ssi_addr
>>
>> indicate the testsuite timed out when gdb was instructed to write the
>> core file. The patch below fixes the problem by simply increasing the
>> timeout by a factor of 2 to give gdb more time to generate core files.
>>
>> Tested in sparc64-linux-gnu. No regressions.
>>     
>
> Did you see timeout fails in all gcore related tests?  gdb_gcore_cmd is
> used in many places in gdb testsuite.  Did you investigate why it is so
> slow to generate coredump in gdb?
>
>   
No, only this test failed with timeout and did so consistently. The 
generated core file was fine.
We suspect the slow disk performance was the culprit.

Thanks.


  reply	other threads:[~2017-03-16 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  3:23 Weimin Pan
2017-03-16 14:45 ` Yao Qi
2017-03-16 16:00   ` Wei-min Pan [this message]
2017-03-16 17:08     ` Pedro Alves
2017-03-16 18:27       ` Wei-min Pan
2017-03-16 18:34         ` Pedro Alves
2017-03-16 19:10           ` Wei-min Pan
2017-03-16 19:21             ` Pedro Alves
2017-03-16 19:51               ` Wei-min Pan

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=58CAB698.7040602@oracle.com \
    --to=weimin.pan@oracle.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