This is the mail archive of the 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: [GCC PR55056] Re: [RFC patch] testsuite: Workaround issues with GCC 4.8.0pre + gdb.trace new KFAIL

On Tue, 09 Sep 2014 23:17:12 +0200, Doug Evans wrote:
> Have you thought of how you might do it differently now?

gcc-4.4.7-4.el6.x86_64 at least for restore.exp produces with line 75:
	gdb_test "info addr l$var"
only patterns:
	Symbol "l\d+" is a variable in $r\d+.

While gcc-4.9.1-7.fc21.x86_64 with the patch of mine we discuss here produces
in half the cases:
	Symbol "l1" is a complex DWARF expression: 0: DW_OP_fbreg -44
And therefore the testcase no longer really tests the GDB feature.

Therefore proposing to make it x86_64 arch specific testcase with
gcc-4.4.7-4.el6.x86_64-precompiled .S file.

For the test I tried only restore.exp now, I will check more the others.

Another possibility would be to make the testcase -Og compatible as GCC
hackers in
say that the variables then should not be <optimized out>.
I have tested that with -Og the testcase currently FAILs already on various
line-matching issues.  But I find the arch-specific .S file safer.


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