Bug 24788
Summary: | Two occurances in libc.so.6 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Horler <mbga8csh> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | fweimer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-24 00:32:13 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: |
Description
Chris Horler
2001-01-24 00:32:10 UTC
The first case looks like a bug in xf86cfg, the fact that you see it crashing in strlen just means that xf86cfg called strlen with some bogus or NULL pointer. The latter again has nothing to do with glibc, if you look carefully into the backtrace, there was a segfault signal received at #3 and #0-#2 happen in the crash handler which catches the segfault. Please submit this as 2 bugreports for the appropriate components and include full details on how can it be reproduced. |