Re: glibc regression on alpha with 2.34+

Hi!

On 11/13/22 00:45, John Paul Adrian Glaubitz wrote:
> I just noticed that there is a regression in glibc on alpha with version 2.34 or later.
> 
> Looking at the build logs for Debian's 2.34-8 [1], 2.35-4 [2] and 2.36-4 [3], it's obvious
> there is something wrong given the many "Segmentation Fault" errors.

This regression was introduced by the following commit:

6c57d320484988e87e446e2e60ce42816bf51d53 is the first bad commit
commit 6c57d320484988e87e446e2e60ce42816bf51d53
Author: H.J. Lu <[email protected]>
Date:   Mon Feb 1 11:00:38 2021 -0800

     sysconf: Add _SC_MINSIGSTKSZ/_SC_SIGSTKSZ [BZ #20305]
     
     Add _SC_MINSIGSTKSZ for the minimum signal stack size derived from
     AT_MINSIGSTKSZ, which is the minimum number of bytes of free stack
     space required in order to gurantee successful, non-nested handling
     of a single signal whose handler is an empty function, and _SC_SIGSTKSZ
     which is the suggested minimum number of bytes of stack space required
     for a signal stack.

FWIW, it does not seem to affect alpha systems with a higher baseline such as EV67.

Adrian

>> [1] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=alpha&ver=2.34-8&stamp=1662963628&raw=0
>> [2] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=alpha&ver=2.35-4&stamp=1666729919&raw=0
>> [3] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=alpha&ver=2.36-4&stamp=1667607306&raw=0
>> [4] https://sourceware.org/bugzilla/show_bug.cgi?id=29575