[SOLVED] Antergos libpthread causes segmentation faults

Osterzone · 06-21-2015, 04:27 AM

A lot of the programs I use on my machine exit with segfaults. Nearly all programs function normally until being closed, at which point they segfault. So far the only two programs that have not worked because of this issue are VLC and Cinnamon, while many other programs like firefox and chromium are affected, but only segfault on what would have been a normal exit.

This does not seem to be a problem with my RAM. I removed all RAM from my machine and replaced it with one known good stick, but the problem persisted.

On running the affected programs with gdb, all seem to return the same trace.

Code:

    Program received signal SIGSEGV, Segmentation fault.
    0x00007ffff79af080 in __lll_unlock_elision () from /usr/lib/libpthread.so.0

So I am led to believe that the root of the problem is in libpthread. I am currently running glibc version 2.21. Please ask anything more you wish to know, and help if you can. Thank you.

dijetlo · 06-23-2015, 10:00 PM

I think I found your problem... from the Antergos site

Quote:

Rolling Release
Antergos is a rolling release distribution. Your entire system, from the base OS components to the applications that you install, will receive updates as they are released upstreamwith only a minimal delay to ensure stability.

That never works.

Ranamon · 06-26-2015, 04:11 PM

Quote:

Originally Posted by Osterzone

A lot of the programs I use on my machine exit with segfaults. Nearly all programs function normally until being closed, at which point they segfault. So far the only two programs that have not worked because of this issue are VLC and Cinnamon, while many other programs like firefox and chromium are affected, but only segfault on what would have been a normal exit.

This does not seem to be a problem with my RAM. I removed all RAM from my machine and replaced it with one known good stick, but the problem persisted.

On running the affected programs with gdb, all seem to return the same trace.

Code:

    Program received signal SIGSEGV, Segmentation fault.
    0x00007ffff79af080 in __lll_unlock_elision () from /usr/lib/libpthread.so.0

So I am led to believe that the root of the problem is in libpthread. I am currently running glibc version 2.21. Please ask anything more you wish to know, and help if you can. Thank you.

I've done a lot of programming in Linux, and the only time I've ever seen programs close with segfaults is due to one of two things: trying to double delete pointers or null pointers (coding errors) or linking to out dated libraries after compiling against newer versions, or vice versa. I've seen it happen with my own programs, and from ones like VCL. If the stack trace points to something in /usr/lib, then the fault's with library incompatibility.

Quote:

Rolling Release

Antergos is a rolling release distribution. Your entire system, from the base OS components to the applications that you install, will receive updates as they are released upstreamwith only a minimal delay to ensure stability.

Classic SLAGIATT (Seemed Like A Good Idea At The Time). Rolling releases and auto updating never turns out well. I tend to use a release until I start getting complaints about out dated libs. Then I blow the whole thing away and install a fresher version. If you want to keep using Antergos, then disable that.

Osterzone · 07-04-2015, 05:28 AM

Okay guys thanks for the non-help. I've used rolling release distros for years and been fine with them.

I had to install the latest intel microcode to ensure stability with my Haswell processor. More info on the process here https://wiki.archlinux.org/index.php/Microcode for anyone googling this issue in the future.