This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/17495] strcmp strncmp over-reads, may cause SIGSEGV
- From: "tstark at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 20 Oct 2014 15:14:16 +0000
- Subject: [Bug libc/17495] strcmp strncmp over-reads, may cause SIGSEGV
- Auto-submitted: auto-generated
- References: <bug-17495-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17495
--- Comment #2 from Tomer Stark <tstark at gmail dot com> ---
(In reply to Andreas Schwab from comment #1)
> This is not a bug, both strcmp and strncmp verify that they never read past
> a page boundary. The attached test case does not crash for me.
I'm clearly getting a segmentation fault with this test case, and simply by
changing the offset variable to a multiple of 32 prevents the segfault.
Similar claims have been made in bugs 12077 and 12597, possibly more that I
can't find.
Is there any further data I can supply to corroborate my claim?
--
You are receiving this mail because:
You are on the CC list for the bug.