AMM
2014-Dec-01 10:41 UTC
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote:> On 11/30/2014 05:53 AM, AMM wrote: >> __strspn_sse42 (in /lib64/libc-2.14.90.so) > Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 > Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). > > If possible, upgrade your valgrind, libc etc. > > br, > Teemu HuovilaThank you for reply. But Dovecot 2.2.10 (and earlier versions) were not throwing this error. Can I can ignore it by NOT doing "make check"? OR is it something serious that if I ignore it can corrupt mailboxes? Unfortunately for some reasons I can not update libc or valgrind. Amm
Teemu Huovila
2014-Dec-01 11:54 UTC
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On 12/01/2014 12:41 PM, AMM wrote:> > On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > But Dovecot 2.2.10 (and earlier versions) were not throwing this error.This test was added in Dovecot version 2.2.14. It is also the only reference to strspn() in the whole project.> Can I can ignore it by NOT doing "make check"?I would say you can safely ignore it, but I can give no guarantee. I have no access to a Fedora 16 system, so I can not verify it, but I would say this is most likely a manifestation of the valgrind bug I linked in my first email. You could try verification yourself, by using the "Steps to Reproduce" in the linked issue tracker. br, Teemu Huovila
AMM
2014-Dec-01 12:36 UTC
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On Monday 01 December 2014 05:24 PM, Teemu Huovila wrote:> On 12/01/2014 12:41 PM, AMM wrote: >> On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: >> But Dovecot 2.2.10 (and earlier versions) were not throwing this error. > This test was added in Dovecot version 2.2.14. It is also the only reference to strspn() in the whole project. > ... > You could try verification yourself, by using the "Steps to Reproduce" in the linked issue tracker. > > br, > Teemu HuovilaVerified it. It is indeed valgrind bug. Thanks for the help. Amm.
Maybe Matching Threads
- v2.2.15 - make check - Conditional jump or move depends on uninitialised value
- v2.2.15 - make check - Conditional jump or move depends on uninitialised value
- v2.2.15 - make check - Conditional jump or move depends on uninitialised value
- Conditional jump or move depends on uninitialised value
- [LLVMdev] Conditional jump or move depends on uninitialised value