From: "Heckel, Bernhard" <bernhard.heckel@intel.com>
To: Luis Machado <lgustavo@codesourcery.com>, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: Fix timeout issues during print of vla-arrays.
Date: Wed, 24 Feb 2016 08:03:00 -0000 [thread overview]
Message-ID: <56CD63CD.7050904@intel.com> (raw)
In-Reply-To: <56CCB4FF.6040803@codesourcery.com>
On 23/02/2016 20:37, Luis Machado wrote:
> On 02/22/2016 11:49 AM, Bernhard Heckel wrote:
>> From: "bernhard.heckel" <bernhard.heckel@intel.com>
>>
>> Printing and resolving of dynamic array's causes sporadic timeout
>> issues on loaded systems.
>>
>> 2016-02-12 Bernhard Heckel <bernhard.heckel@intel.com>
>>
>> gdb/Changelog:
>>
>> * vla-history.exp: Lookup array elements and printing exceeds
>> timeout.
>>
>>
>> Conflicts:
>>
>> gdb/testsuite/gdb.fortran/vla-history.exp
>> gdb/testsuite/gdb.fortran/vla-value.exp
>> ---
>> gdb/testsuite/gdb.fortran/vla-history.exp | 17 +++++++++--------
>> 1 file changed, 9 insertions(+), 8 deletions(-)
>>
>> diff --git a/gdb/testsuite/gdb.fortran/vla-history.exp
>> b/gdb/testsuite/gdb.fortran/vla-history.exp
>> index 1478e6b..2012961 100644
>> --- a/gdb/testsuite/gdb.fortran/vla-history.exp
>> +++ b/gdb/testsuite/gdb.fortran/vla-history.exp
>> @@ -30,19 +30,20 @@ gdb_breakpoint [gdb_get_line_number "vla1-init"]
>> gdb_continue_to_breakpoint "vla1-init"
>> gdb_test "print vla1" " = <not allocated>" "print non-allocated vla1"
>>
>> -gdb_breakpoint [gdb_get_line_number "vla2-allocated"]
>> -gdb_continue_to_breakpoint "vla2-allocated"
>> -
>
> Is the change above spurious? I see code being moved to higher timeout
> blocks, but the above doesn't seem to reappear anywhere. It was just
> deleted.
>
> Did it cause problems?
The vla2-allocated breakpoint was not used at all therefore I removed it
from the test script when I investigated on the timeout issue. There
were no problems with the breakpoint.
Regards,
Bernhard
--
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2016-02-24 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:49 [PATCH] Fix detection of gfortran compilers Bernhard Heckel
2016-02-22 14:50 ` [PATCH] testsuite: Fix timeout issues during print of vla-arrays Bernhard Heckel
2016-02-23 19:37 ` Luis Machado
2016-02-24 8:03 ` Heckel, Bernhard [this message]
2016-02-24 14:47 ` Yao Qi
2016-02-25 13:16 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Fix run to main issue introduced by GCC 5.x Bernhard Heckel
2016-02-26 16:55 ` Joel Brobecker
2016-03-02 15:44 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Nullify pointers before first usage Bernhard Heckel
2016-02-26 16:49 ` Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
2016-02-26 16:47 ` [PATCH] Fix detection of gfortran compilers Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
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=56CD63CD.7050904@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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