/usr/lib/go/pkg/tool/linux_amd64/buildid -w $WORK/b001/exe/a.out # internal cp $WORK/b001/exe/a.out ipfswatch rm -r $WORK/b001/ unexpected fault address 0x22c4be0 fatal error: fault [signal SIGSEGV: segmentation violation code=0x2 addr=0x22c4be0 pc=0xd80120] ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j4-20221028-130004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12 * clang/llvm (if any): /usr/lib/llvm/13 13.0.1 Python 3.10.8 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.64.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.4.1_p1 [openjdk-bin-17] 2) Eclipse Temurin JDK 8.345_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 system-vm The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): GNU Make 4.3 HEAD of ::gentoo commit 8116f5349c6d5f1a239a91308445a42a1186d6d1 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Oct 28 20:46:52 2022 +0000 2022-10-28 20:46:52 UTC emerge -qpvO net-p2p/kubo [ebuild N ] net-p2p/kubo-0.15.0
Created attachment 825787 [details] emerge-info.txt
Created attachment 825789 [details] emerge-history.txt
Created attachment 825791 [details] environment
Created attachment 825793 [details] etc.portage.tar.bz2
Created attachment 825795 [details] logs.tar.bz2
Created attachment 825797 [details] net-p2p:kubo-0.15.0:20221028-211950.log.bz2
Note: It happens because ipfswatch operates recursively by default and on big directory trees it may crash. But I believe it's pretty hard some real user are hit by this issue. So I am ignoring this until I have enough spare time to look into this or some real person is hit by this.
Actually the issue occur when a broken link is found. I opened an issue upstream https://github.com/ipfs/kubo/issues/10017