Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 429450 - sys-apps/hwinfo-19.1 - hwinfo[NNNNN]: segfault at NNN ip NNNNNNNNNNNNNNNN sp NNNNNNNNNNNNNNNN error 4 in[NNNNNNNNNNNN+NNNNN]
Summary: sys-apps/hwinfo-19.1 - hwinfo[NNNNN]: segfault at NNN ip NNNNNNNNNNNNNNNN sp ...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Ben Kohler
Keywords: PATCH
Depends on:
Blocks: 422173
  Show dependency tree
Reported: 2012-08-02 08:24 UTC by crucify
Modified: 2021-03-23 19:53 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

hwinfo-19.1.patch (hwinfo-19.1.patch,535 bytes, patch)
2012-08-02 08:25 UTC, crucify
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description crucify 2012-08-02 08:24:37 UTC
segmentation fault patch file

Reproducible: Always
Comment 1 crucify 2012-08-02 08:25:35 UTC
Created attachment 320024 [details, diff]
Comment 2 Agostino Sarubbo gentoo-dev 2012-08-05 19:14:15 UTC
Can't reproduce, fine here
Comment 3 Ben Kohler gentoo-dev 2012-12-23 19:25:27 UTC
I have seen this kind of behavior from time to time, depending on my CFLAGS & CPU type.  For quite a while I was forcing CFLAGS="" on this package to prevent segfaults.  Working fine right now, though.  We need to see crucify's emerge --info to have a chance to reproduce this.
Comment 4 Bartosz Brachaczek 2013-01-06 21:55:18 UTC
I've also seen it on my machine. It was fine with -O0 (or just empty CFLAGS), and it was starting to fail with -O1 and higher. But now after several days it calmed down, it just works with each flag combination, I can't explain it.

I guess we need to contact someone with amd64 asm knowledge or just the upstream to review crucify's patch.
Comment 5 Ben Kohler gentoo-dev 2021-03-23 19:53:36 UTC
The code this patch touches has been heavily modified since then, can you please reopen if this still affects 21.72?