[Expired for glibc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: glibc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773796
T
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 actuall
** Description changed:
I am developing a custom program which used to work without errors in
Ubuntu 16.04, but crashes very often in the current release. The core
- dump says the segmentation fault occurs in "__strcmp_ssse3", which is
+ dump says the segmentation fault occurs in __strcmp_ssse
