public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* glibc 2.36 make check
@ 2022-08-03 12:46 Michael Brunnbauer
  2022-08-04 14:37 ` Adhemerval Zanella Netto
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Brunnbauer @ 2022-08-03 12:46 UTC (permalink / raw)
  To: libc-help


[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]


hi all,

make check with the new version of glibc has two new failures on my custom
system:

 FAIL: misc/tst-mount-consts

From misc/tst-mount-consts.out:

 test.c:2:10: fatal error: linux/mount.h: No such file or directory
  #include <linux/mount.h>

/usr/include/linux/mount.h is indeed missing and I checked that 
make headers_install with my current kernel would not change that.

 FAIL: nptl/tst-pthread-gdb-attach-static

I have attached the file nptl/tst-pthread-gdb-attach-static.out.

Should I worry about those new failed tests?

Here is some data about my setup:

-glibc configure options:
 --prefix=/usr --enable-kernel=4.9.0 --host=x86_64-pc-linux-gnu --disable-experimental-malloc
-kernel version: 4.9.320
-installed kernel headers: from some older 4.9.x kernel
-gcc version: 7.5.0
-gdb version 9.1

Regards,

Michael Brunnbauer

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni@netestate.de
++  https://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel

[-- Attachment #1.2: tst-pthread-gdb-attach-static.out --]
[-- Type: text/plain, Size: 2295 bytes --]

+set debug libthread-db 1
+set auto-load safe-path /home/bold/base/glibc-2.36/compile/nptl_db
+set libthread-db-search-path /home/bold/base/glibc-2.36/compile/nptl_db
+attach 15009
[New LWP 15010]
BFD: /home/bold/base/glibc-2.36/compile/nptl/tst-pthread-gdb-attach-static: unknown type [0x13] section `.relr.dyn'
Trying host libthread_db library: /home/bold/base/glibc-2.36/compile/nptl_db/libthread_db.so.1.
td_ta_new failed: generic error
thread_db_load_search returning 0
Trying host libthread_db library: /home/bold/base/glibc-2.36/compile/nptl_db/libthread_db.so.1.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/home/bold/base/glibc-2.36/compile/nptl_db/libthread_db.so.1".
thread_db_load_search returning 1
0x00007f7108944d0d in __futex_abstimed_wait_common64 (private=<optimized out>, cancel=true, abstime=<error reading variable: Cannot access memory at address 0x8f6ef888>, op=<error reading variable: Cannot access memory at address 0x8f6ef878>, expected=15010, futex_word=<error reading variable: Cannot access memory at address 0x8f6ef880>) at futex-internal.c:57
57	    return INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected,
+break debugger_inspection_point
Breakpoint 1 at 0x88c95d0: file tst-pthread-gdb-attach.c, line 126.
+continue
[Switching to Thread 0x7f71088c66c0 (LWP 15010)]

Thread 2 "tst-pthread-gdb" hit Breakpoint 1, debugger_inspection_point () at tst-pthread-gdb-attach.c:126
126	{
+thread 1
[Switching to thread 1 (Thread 0x7f71089ae380 (LWP 15009))]
#0  0x00007f7108944d0d in __futex_abstimed_wait_common64 (private=<optimized out>, cancel=true, abstime=<error reading variable: Cannot access memory at address 0x8f6ef888>, op=<error reading variable: Cannot access memory at address 0x8f6ef878>, expected=15010, futex_word=<error reading variable: Cannot access memory at address 0x8f6ef880>) at futex-internal.c:57
57	    return INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected,
+print altered_by_debugger
/tmp/tst-pthread-gdb-attach-kqWILN:9: Error in sourced command file:
Cannot access memory at address 0x89ae340
[Inferior 1 (process 15009) detached]
tst-pthread-gdb-attach.c:229: numeric comparison failure
   left: 256 (0x100); from: status
  right: 0 (0x0); from: 0
error: 1 test failures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: glibc 2.36 make check
  2022-08-03 12:46 glibc 2.36 make check Michael Brunnbauer
@ 2022-08-04 14:37 ` Adhemerval Zanella Netto
  0 siblings, 0 replies; 2+ messages in thread
From: Adhemerval Zanella Netto @ 2022-08-04 14:37 UTC (permalink / raw)
  To: Michael Brunnbauer, libc-help



On 03/08/22 09:46, Michael Brunnbauer wrote:
> 
> hi all,
> 
> make check with the new version of glibc has two new failures on my custom
> system:
> 
>  FAIL: misc/tst-mount-consts
> 
> From misc/tst-mount-consts.out:
> 
>  test.c:2:10: fatal error: linux/mount.h: No such file or directory
>   #include <linux/mount.h>
> 
> /usr/include/linux/mount.h is indeed missing and I checked that 
> make headers_install with my current kernel would not change that.

The header was added only at 5.0 version, we will need to set the test unsupported
if the headers is not present.

> 
>  FAIL: nptl/tst-pthread-gdb-attach-static
> 
> I have attached the file nptl/tst-pthread-gdb-attach-static.out.

This is unexpected, although the log is not clear.  I am not sure sure if this is
gdb issue in fact.

> 
> Should I worry about those new failed tests?
> 
> Here is some data about my setup:
> 
> -glibc configure options:
>  --prefix=/usr --enable-kernel=4.9.0 --host=x86_64-pc-linux-gnu --disable-experimental-malloc
> -kernel version: 4.9.320
> -installed kernel headers: from some older 4.9.x kernel
> -gcc version: 7.5.0
> -gdb version 9.1
> 
> Regards,
> 
> Michael Brunnbauer
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-08-04 14:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-03 12:46 glibc 2.36 make check Michael Brunnbauer
2022-08-04 14:37 ` Adhemerval Zanella Netto

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).