Following up on the autopkgtest regression: the SIGSEGV in scalpel is
reproducible with just the packages in jammy and jammy-updates.
You can see that a migration-reference [1] fails with SIGSEGV.
I reproduced the issue by hand as well. I spun up a jammy container
containing scalpel
```
#!/bin/bash
CTR_NAME="reproduce-scalpel-failure"
cleanup() {
lxc stop $CTR_NAME
}
trap cleanup EXIT
lxc launch -e ubuntu:jammy $CTR_NAME
lxc exec $CTR_NAME -- apt update -y
lxc exec $CTR_NAME -- apt install scalpel -y
lxc exec $CTR_NAME -- su -l ubuntu
```
Then I just ran
`scalpel -o "$(mkdir -d)" DOES-NOT-EXIST`
a few times and intermittently obtained a segfault.
So, I don't think the autopkgtest regression is related to this glibc
patch since it happens reproduceably without the patch.
[1]: https://autopkgtest.ubuntu.com/packages/s/scalpel/jammy/amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089789
Title:
malloc performance degradation with CPU affinity masks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2089789/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
