This is the mail archive of the frysk@sources.redhat.com mailing list for the frysk 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: Test result of utrace on PPC64(based on Fedoracore 6 Test 2 release).


Roland McGrath wrote:
Please try applying this patch to your gdb source.  This is in my gdb tree
and I think it was to fix a latent testsuite bug I found.  If it helps for
you, I'll make sure to get it in upstream.

I applied your patch. This can fix one FAIL in gdb/auxv.exp when running in 32-bit mode, no matter that the kernel be ptrace or utrace. But the extra error (matching auxv data from live and gcore) of auxv.exp have no relation with this. The root cause is that the output of "info auxv" on gcore have one line different than that of live code:


15 AT_PLATFORM String identifying platform 0xfa61fa89 <Address 0xfa61fa89 out of bounds>

which should be:
 15   AT_PLATFORM          String identifying platform    0xff9e54a5 "power5+"

Also make sure you do "ulimit -c unlimited" before all test runs.
Some of the diffs look like one of the runs did not have that done.

For 32-bit testcase, we did do that. A few failure on 64-bit testcase is attributed to not running "ulimit -c unlimited" before the testcase.


Please try using the most current rawhide kernel you can get.

We had another run with kernel 2.6.17-1.2583.fc6. It is mostly the same, in fact, a few more regression in failing cases. Don't do any more analysis yet.


We will try the test a few days later to see what will happen.

Regards
- Wu Zhou



Thanks,
Roland


--- testsuite/gdb.base/auxv.exp 24 Jul 2006 14:20:50 -0000 1.6
+++ testsuite/gdb.base/auxv.exp 22 Aug 2006 05:25:37 -0000
@@ -81,6 +81,7 @@ proc fetch_auxv {test} {
global gdb_prompt
set auxv_lines {}
+ set seen_null 0
set bad -1
if {[gdb_test_multiple "info auxv" $test {
-re "info auxv\[\r\n\]+" {
@@ -99,7 +100,15 @@ proc fetch_auxv {test} {
exp_continue
}
-re "^\[0-9\]+\[ \t\]+(AT_\[^ \t\]+)\[^\r\n\]+\[\r\n\]+" {
+ if {$expect_out(1,string) == "AT_NULL"} {
+ # We can ignore multiple terminators.
+ set seen_null 1
+ } elseif {$seen_null} {
+ warning "Element after AT_NULL: $expect_out(0,string)"
+ set bad 1
+ } else {
lappend auxv_lines $expect_out(0,string)
+ }
exp_continue
}
-re "^\[0-9\]+\[ \t\]+\\?\\?\\?\[^\r\n\]+\[\r\n\]+" {
@@ -122,6 +131,11 @@ proc fetch_auxv {test} {
return {}
}
+ if {!$seen_null} {
+ warning "No AT_NULL terminator element"
+ set bad 1
+ }
+
if {$bad} {
fail $test
return {}


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