[PATCH] gdb.base/siginfo-thread.exp: Increase timeout for 'gcore' command

Pedro Alves palves@redhat.com
Thu Mar 16 19:21:00 GMT 2017


On 03/16/2017 07:10 PM, Wei-min Pan wrote:

>> You mean that by hand it went faster than that?
>> So what is GDB doing differently when run via make check
>> that makes it slower than running by hand?
>>   
> 
> Yes, but not by much faster:
> 
> % cat in
> run
> gcore tmp.gcore
> quit
> 
> % time my_gdb siginfo-thread -x in
> ...
> real    0m13.327s
> user    0m3.504s
> sys     0m7.572s

Either I'm missing something, or that was _slower_ than then
number you shown of running via the testsuite, not faster...

So WDT is GDB doing that takes that long?  Is that writing
the core to a slow NFS mount or something?

Here that takes:

 real    0m0.120s
 user    0m0.090s
 sys     0m0.033s

and this is not a state-of-the-art machine.

Can you guess the next question?

Pick any other core test in the testsuite, do the
same and compare the numbers.

And if they're different, the next question would
then be, "what's different in this test, why's
it slower?".

If they're similar, then, well, the same question.  :-)

Thanks,
Pedro Alves



More information about the Gdb-patches mailing list