Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bernhard Heckel <bernhard.heckel@intel.com>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
	"bernhard.heckel" <bernhard.heckel@intel.com>
Subject: [PATCH] testsuite: Fix timeout issues during print of vla-arrays.
Date: Mon, 22 Feb 2016 14:50:00 -0000	[thread overview]
Message-ID: <1456152558-3962-4-git-send-email-bernhard.heckel@intel.com> (raw)
In-Reply-To: <1456152558-3962-1-git-send-email-bernhard.heckel@intel.com>

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"
-
 gdb_breakpoint [gdb_get_line_number "vla1-filled"]
 gdb_continue_to_breakpoint "vla1-filled"
-gdb_test "print vla1" \
-  " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" \
-  "print vla1 filled"
+with_timeout_factor 2 {
+    gdb_test "print vla1" \
+      " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" \
+      "print vla1 filled"
+}
 
 # Try to access history values for full vla prints.
 gdb_test "print \$1" " = <not allocated>" "print \$1"
-gdb_test "print \$2" \
-  " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" "print \$2"
+with_timeout_factor 2 {
+    gdb_test "print \$2" \
+      " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" "print \$4"
+}
 
 gdb_breakpoint [gdb_get_line_number "vla2-filled"]
 gdb_continue_to_breakpoint "vla2-filled"
-- 
2.7.1.339.g0233b80


  reply	other threads:[~2016-02-22 14:50 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 ` Bernhard Heckel [this message]
2016-02-23 19:37   ` [PATCH] testsuite: Fix timeout issues during print of vla-arrays Luis Machado
2016-02-24  8:03     ` Heckel, Bernhard
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=1456152558-3962-4-git-send-email-bernhard.heckel@intel.com \
    --to=bernhard.heckel@intel.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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