Bug 838155
Summary: | [abrt] coreutils-8.12-7.fc16: __GI_getenv: Process /usr/bin/uniq was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Olivier <olivier> | ||||
Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 16 | CC: | kdudka, maxamillion, ovasik, pbrady, p, twaugh | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:803b15662a6a8b550d1c65a224a153520669e7e4 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-12-13 08:32:46 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Olivier
2012-07-06 20:58:56 UTC
Created attachment 596684 [details]
File: backtrace
That's a strange one. If it is a bug I'd be inclined to think it's against glibc (2.14.90-24.fc16.7.x86_64) There are similar failures in bug #746787 and bug #814235, though they're in multithreaded programs. uniq is not multithreaded, and I don't think implicit threads are created for it. I presume this is not easily reproducible? Based on the backtrace it seems that this may be another flaw in downstream only multibyte i18n patch. Reporter, can you attach the reproducer files, if this issue is easily reproducible for you? Hi Ondrej, Sorry I cannot reproduce this bug. It occured only once just after I logged in. Doing cleanup. Closing this one insufficient data, like Pádraig said, maybe glibc glitch. Because it is not reproducable, for the reporter, further analysis is probably impossible. Feel free to reopen the issue if you'll be able to reproduce this segfault somehow. |