| Summary: | sys-apps/hwinfo-19.1 - hwinfo[NNNNN]: segfault at NNN ip NNNNNNNNNNNNNNNN sp NNNNNNNNNNNNNNNN error 4 in libhd.so.16.0[NNNNNNNNNNNN+NNNNN] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | crucify <shj> |
| Component: | [OLD] Core system | Assignee: | Ben Kohler <bkohler> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | b.brachaczek |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| See Also: |
http://bugs.debian.org/652146 https://bugs.gentoo.org/show_bug.cgi?id=458288 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 422173 | ||
| Attachments: | hwinfo-19.1.patch | ||
|
Description
crucify
2012-08-02 08:24:37 UTC
Created attachment 320024 [details, diff]
hwinfo-19.1.patch
Can't reproduce, fine here 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. 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. The code this patch touches has been heavily modified since then, can you please reopen if this still affects 21.72? Thanks |
