99 times out of 100, a segfault in strcmp() is a bug in the caller,
feeding strcmp() a nonsensical pointer to la-la land. strcmp() itself
doesn't really do much with memory that could lead to a segv, other than
attempt to access the two chars you asked it to look at. If one or both
aren't actually there, you're going to have a bad day.
If you can give me a test case that shows strcmp() itself being fed non-
garbage values and then crashing, please do, but otherwise, I'm marking
this Incomplete for now.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773796
Title:
Segmentation fault in __strcmp_ssse3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1773796/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
