Re: glibc regression on alpha with 2.34+

Frank Scheiner <[email protected]> Wed, 14 Dec 2022 18:21:53 +0100
Newsgroups gmane.linux.debian.ports.alpha
Message-ID <[email protected]>
Hi Adrian,

On 13.12.22 17:21, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> On 12/13/22 10:52, John Paul Adrian Glaubitz wrote:
>> You could cross-compile glibc. That's most likely what I am going to do.
> 
> For the record, here's how I am doing it.
> 
> [...]

Thanks for that, this is quite useful.

> 4. Enter alpha schroot and run the the following command from the build 
> directory:
> 
>     (sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$ 
> LD_LIBRARY_PATH=/home/glaubitz/glibc-git/build /bin/bash
> 
>     If the bug is present, this command will segfault:
> 
>     Segmentation fault
> 
>     Otherwise it will just spawn another bash which can be exited with 
> "exit":
> 
>     (sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$ 
> LD_LIBRARY_PATH=/home/glaubitz/glibc-git/build /bin/bash
>     (sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$
>     exit
>     (sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$

Can we be sure that this reproducer identifies the same problem than the 
build failures from the original post ([1])?

[1]: https://lists.debian.org/debian-alpha/2022/11/msg00003.html

Regardless, I can confirm this on my DS15:

```
root@ds15:/srv/storage/build# 
LD_LIBRARY_PATH=$PWD/glibc-at-36231bee7ab36d59dd121ea85b91411ae86945f3 
/bin/bash
root@ds15:/srv/storage/build# echo $?
0
root@ds15:/srv/storage/build# exit
exit

root@ds15:/srv/storage/build# 
LD_LIBRARY_PATH=$PWD/glibc-at-6c57d320484988e87e446e2e60ce42816bf51d53 
/bin/bash
Segmentation fault
root@ds15:/srv/storage/build# echo $?
139
```

...6c57d320484988e87e446e2e60ce42816bf51d53 is the first bad commit and 
36231bee7ab36d59dd121ea85b91411ae86945f3 is its parent.

Do we also have a result for 
glibc@6c57d320484988e87e446e2e60ce42816bf51d53 with `-mcpu=ev67`?

Cheers,
Frank