Bug#1076512: glibc: FTBFS on hppa - stdlib/tst-swapcontext2 test fails

[John David Anglin <dave@parisc-linux.org>]

Source: glibc
Version: 2.39-4
Severity: normal
Tags: ftbfs

Dear Maintainer,

Build filas here:

----------
FAIL: stdlib/tst-swapcontext2
original exit status 1
  [31mfunc1: func3(&uctx_func1, &uctx_main, str1)[0m
    [31mfunc3: func4(uocp, ucp, str)[0m
      [31mfunc4: [31mswapcontext(&uctx_func1, &uctx_main)[0m[0m
        [35mmain: swapcontext(&uctx_main, &uctx_func2)
[0m  [34mfunc2: func3(&uctx_func2, &uctx_main, str2)[0m
    [34mfunc3: func4(uocp, ucp, str)[0m
      [34mfunc4: [34mswapcontext(&uctx_func2, &uctx_main)[0m[0m
        [35mmain: swapcontext(&uctx_main, &uctx_func1)
[0m      [31mfunc4: returning[0m
    [31mfunc3: returning[0m
  [31mfunc1: func3(&uctx_func1, &uctx_main, str1)[0m
    [31mfunc3: func4(uocp, ucp, str)[0m
      [31mfunc4: [31mswapcontext(&uctx_func1, &uctx_main)[0m[0m
        [35mmain: swapcontext(&uctx_main, &uctx_func2)
[0m      [34mfunc4: returning[0m
    [34mfunc3: returning[0m
    [34mfunc2: calling longjmp[0m
Didn't expect signal from child: got `Aborted'
----------
+---------------------------------------------------------------------+
|     Encountered regressions that don't match expected failures.     |
+---------------------------------------------------------------------+
FAIL: stdlib/tst-swapcontext2
touch /<<PKGBUILDDIR>>/stamp-dir/check_libc
CHECK SUMMARY
check for check_libc failed

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=hppa&ver=2.39-4&stamp=1721152208&raw=0

dave@atlas:~/gnu/glibc/objdir/stdlib$ ./tst-swapcontext2
  func1: func3(&uctx_func1, &uctx_main, str1)
    func3: func4(uocp, ucp, str)
      func4: swapcontext(&uctx_func1, &uctx_main)
        main: swapcontext(&uctx_main, &uctx_func2)
  func2: func3(&uctx_func2, &uctx_main, str2)
    func3: func4(uocp, ucp, str)
      func4: swapcontext(&uctx_func2, &uctx_main)
        main: swapcontext(&uctx_main, &uctx_func1)
      func4: returning
    func3: returning
  func1: func3(&uctx_func1, &uctx_main, str1)
    func3: func4(uocp, ucp, str)
      func4: swapcontext(&uctx_func1, &uctx_main)
        main: swapcontext(&uctx_main, &uctx_func2)
      func4: returning
    func3: returning
    func2: calling longjmp
*** longjmp causes uninitialized stack frame ***: terminated
Didn't expect signal from child: got `Aborted'

This bug is enabled by the --enable-fortify-source configure option.

This needs more research to determine whether this fail is caused
by a real problem (hppa is the only architecure where the stack
grows upward).  I think for now we should xfail the test.

Regards,
Dave Anglin

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 6.9.9-dirty (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)