Skip to content
← Back to activity

Solution skill

Possible glibc issue on x86_64 linux systems

Version 2Sign in to save

Complete solution

Shows how to fix possible glibc issue on x86_64 linux systems. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Bearer segfaulting on x86_64 Linux was fixed in Bearer 1.4.0. If the scanner crashes with segfaults on Linux, upgrade to 1.4.0 or later and confirm the crashes are gone.

Steps

  1. Bearer segfaulting on x86_64 Linux was fixed in Bearer 1.4.0.
  2. If the scanner crashes with segfaults on Linux, upgrade to 1.4.0 or later and confirm the crashes are gone.

When to use

You are seeing this: Issue Bearer/bearer#899 (closed, 8 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description Currently on linux it looks like we are seeing some segfaults with some users that have the x86\64 instruction set. Use this skill when you run into "Possible glibc issue on x8664 linux systems".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: hostname 5.10.0-21, Debian 5.10.162-1, Bearer 1.4.0. If you are on something much newer or older, the details may have shifted.

Why this happens

Issue Bearer/bearer#899 (closed, 8 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description Currently on linux it looks like we are seeing some segfaults with some users that have the x86\_64 instruction set.

Sources

  • https://github.com/Bearer/bearer/blob/main/.goreleaser/common.yaml#L52-L56
  • https://github.com/Bearer/bearer/issues/899

Evidence

In gh:Bearer/bearer#899, the reporter ran into: Issue Bearer/bearer#899 (closed, 8 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description Currently on linux it looks like we are seeing some segfaults with some users that have the x86_64 instruction set. This is somewhat unexpected as we compile for amd64 here which should be compatible ## uname -a works: ``` Linux hostname 5.10.0-21-amd64 #1 MP Debian 5.10.162-1 (2023-01-21) x8664 GNU/Linux Linux hostname 5.15. The verified answer was: Bearer segfaulting on x8664 Linux was fixed in Bearer 1.4.0. If the scanner crashes with segfaults on Linux, upgrade to 1.4.0 or later and confirm the crashes are gone. Source issue: https://github.com/Bearer/bearer/issues/899

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vP7njRmu7lZ3wpjCxhVIcw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Possible glibc issue on x86_64 linux systems <span>— Vectle</span></a>

Possible glibc issue on x86_64 linux systems | Vectle