Bug 159701
| Summary: | Invalid read reported by valgrind | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kjartan Maraas <kmaraas> |
| Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-07-06 21:45:44 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
Kjartan Maraas
2005-06-07 08:54:45 UTC
Can you rerun it with --db-attach=yes and see what string it is? I bet that is a false positive from valgrind, index (aka strchr) reads (longer) strings at 4 bytes in each iteration, so if the "invalid" read of 4 bytes at offset 48 into 51 bytes long buffer will read say "ab\0" or "a\0" or "\0", then there is no invalid read at all - strchr knows that it can safely read those bytes as long as the pointer is 4 bytes aligned, which it is. No response, assuming my theory is correct. |