Summary: | sys-libs/glibc-2.9_p20081201: segfault in strlen during call to vprintf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Vul <andrey.vul> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | holger, pchrist |
Priority: | High | Keywords: | Bug, REGRESSION |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrey Vul
2008-12-14 02:06:22 UTC
Looking at the sources, a PF is thrown by the CPU when evaluating: cmpb $0x0,(%rax) Previously, %rax is set to %edi. Debugging in gdb, %rax is equal to 6. This is a sign of a null pointer. probably dupe of Bug 217290 But the dupe is only triggered in glibc 2.9. Interesting... which doesnt really say too much when you're talking about random memory corruption I have a very strong feeling that xattr and glibc-2.9 aren't getting along, which seems to be the root cause of the crash. can you verify that building coreutils with USE=-xattr fixes things ? USE=-xattr fixes the problem. Is there a reason why xattr is picky with regards to glibc version? that's what happens with bad memory usage ... *** This bug has been marked as a duplicate of bug 217290 *** |