This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] testsuite: Fix timeout issues during print of vla-arrays.


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?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]