FS#69422 - [bcc] All tools segfault

Attached to Project: Community Packages
Opened by Christian Pellegrin (chripell) - Sunday, 24 January 2021, 09:56 GMT
Last edited by Toolybird (Toolybird) - Sunday, 07 May 2023, 05:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description: All the tools segfault, I am adding a backtracewhich points to a problem in the lbbcc library. If I recompile the packages from ABS, the problem goes away. I suspect some CPU flag sneaked into the build.

Additional info:
* package version(s)

0.18.0-1

* config and/or log files etc.

Adding the backtrace and my cpuinfo.

* link to upstream bug report, if any

Could not find anything

Steps to reproduce:

Just run any tool, for example opensnoop. It segfaults.

Thanks!
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 07 May 2023, 05:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  Stale. Seems to work fine currently.
Comment by Doug Newgard (Scimmia) - Sunday, 24 January 2021, 13:31 GMT
Looking at the backtrace, I wonder if it's the new clang that causes it.
Comment by Christian Pellegrin (chripell) - Sunday, 24 January 2021, 13:49 GMT
For the working recompilation I used:

[chri@fudoh ~]$ clang --version
clang version 11.0.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

and I am attaching my local makepkg.conf. Please note that I had to disable -j4, because it triggers a problem with luajit dependencies (/usr/bin/luajit: unknown luaJIT command or jit.* modules not installed). I remember having this problem since when bcc was in AUR. Regrettably, I've haven't looked into it yet :-(

If you need that I do any other tests, just let me know. I will have a look into the clang upstream if I can find something.

Loading...