Hi Michael,
On 01/10/2023 14:22, Michael Tremer wrote:
Hello,
On 30 Sep 2023, at 13:39, Adolf Belka adolf.belka@ipfire.org wrote:
Hi Michael,
I just ran git pull which took me to commit
build: Add implicit dist() when a makefile is passed -- followed by make and make install.
Running pakfire-builder build beep/beep.nm gave the error message "Segmentation fault"
I can confirm this, but it seems to be a crash in libcurl/glibc:
Rolling back to
cli: pakfire-builder: Implement "image create"
then worked with beep fine.
However, if you say rolling back works, then we must trigger the crash in Pakfire somehow, because libcurl/glibc stays the same.
My earlier rolling back worked. However when I then tried to create a new package, python3-build, it then segfaulted again.
Then I rolled back a long way and tried again with the python3-build and again it segfaulted.
So it looks like the segfault is not always consistent but rolling back did not actually help as there are still packages that end up with a segfault.
Regards, Adolf.
In IPFire we use c-ares as a resolver for cURL which does not crash like this.
Then tried git pull, make, make install again and this time beep built without any problems. Then I tried sqlite and I got the segmentation fault again.
This is very early when Pakfire is starting up and refreshing its repository information.
Then I rolled back and sqlite built okay. Then ran sqlite again and this time part way through building my laptop logged out from my session.
Logged back in and ran sqlite again and this after a short while everything froze and I had to reset the laptop.
So rolling back to
cli: pakfire-builder: Implement "image create"
Does not stop the problem happening it just seems to show itself in different forms.
I have now rolled back to
cli: pakfire: Implement --yes
which I think is where my last git pull had placed me.
Running pakfire-builder on beep twice and sqlite four times has given no problems so that commit stage is confirmed good.
Let me know if there is anything else I should try to narrow the problem down.
Good question. I have a VM with archlinux where I can reproduce the crash. I will have a look what I can do to fix this…
-Michael
Regards, Adolf.
-- Sent from my laptop