Re: glibc 2.23 testsuite issues on hppa
On 2016-06-30, at 7:25 PM, Aurelien Jarno wrote:
> FAIL: nptl/tst-cancel9
> FAIL: nptl/tst-cancelx9
>
> These two errors need some investigation as the build log does not
> provide a lot of details. They seem to be linked as they anyway use the
> same source code with different compilation options.
These two fails are not new and I thought they had been added to XFAIL list. They
were listed as regressions in your mail "glibc 2.22 testsuite issues on hppa" on March 8
and were added to the 2.22 XFAIL list.
They also occur with trunk.
Strangely, these two tests do not fail when run using installed libraries:
dave@mx3210:~/gnu/glibc/objdir/nptl$ ./tst-cancel9
cancel now
waiting for the child
in cleanup
dave@mx3210:~/gnu/glibc/objdir/nptl$ ldd ./tst-cancel9
libpthread.so.0 => /lib/hppa-linux-gnu/libpthread.so.0 (0xfd4d8000)
libc.so.6 => /lib/hppa-linux-gnu/libc.so.6 (0xfd2df000)
/lib/ld.so.1 (0x41000000)
The tests fail due to some kind of race which causes a segmentation fault in the unwind code:
(gdb) r
Starting program: /home/dave/gnu/glibc/objdir/nptl/tst-cancel9
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
[New process 17717]
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
[New LWP 17718]
cancel now
waiting for the child
Thread 3.2 "tst-cancel9" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 17718]
0xfa59afd4 in _Unwind_GetGR (index=2, context=0xfacd3708)
at ../../../src/libgcc/unwind-dw2.c:239
239 ../../../src/libgcc/unwind-dw2.c: No such file or directory.
(gdb) Timed out: killed the child process
bt
#0 0xfa59afd4 in _Unwind_GetGR (
index=<error reading variable: Cannot access memory at address 0xfacd3ebc>, context=0xfacd3708) at ../../../src/libgcc/unwind-dw2.c:239
#1 _Unwind_GetPtr (
index=<error reading variable: Cannot access memory at address 0xfacd3ebc>, context=0xfacd3708) at ../../../src/libgcc/unwind-dw2.c:251
#2 uw_update_context (context=0xfacd3708,
context@entry=<error reading variable: Couldn't read register r6 (#6): No such process.>, fs=fs@entry=0xfacd3bc8) at ../../../src/libgcc/unwind-dw2.c:1518
#3 0xfa59b294 in uw_advance_context (fs=0xfacd3bc8,
context=<error reading variable: Couldn't read register r6 (#6): No such process.>) at ../../../src/libgcc/unwind-dw2.c:1525
#4 _Unwind_ForcedUnwind_Phase2 (
exc=<error reading variable: Couldn't read register r5 (#5): No such process.>,
context=<error reading variable: Couldn't read register r6 (#6): No such process.>) at ../../../src/libgcc/unwind.inc:185
Backtrace stopped: Cannot access memory at address 0xfacd3bac
I tend to think it's a kernel bug.
Dave
--
John David Anglin dave.anglin@bell.net
Reply to: