On 08.08.2018 10:55, Reuben Farrelly wrote:
>
> On 8/08/2018 5:29 pm, Thore Bödecker wrote:
>> Hey,
>>
>> you mentioned that dovecot builds fine, but does "make check" also
>> complete successfully with a glibc-2.28 build on a glibc-2.28 system?
>>
>> We have been seeing segfaults during "make c
On 8/08/2018 5:29 pm, Thore Bödecker wrote:
Hey,
you mentioned that dovecot builds fine, but does "make check" also
complete successfully with a glibc-2.28 build on a glibc-2.28 system?
We have been seeing segfaults during "make check" and it seems the following
patch was able to make the tes
Hey,
you mentioned that dovecot builds fine, but does "make check" also
complete successfully with a glibc-2.28 build on a glibc-2.28 system?
We have been seeing segfaults during "make check" and it seems the following
patch was able to make the testsuite run successfully.
Just out of curiosity,
Was able to find a way to get glibc-2.28 and it seems that they have
changed how crypt return value behaves.
I am not sure if this is intentional or not, but it appears that the
return value becomes invalidated as soon as function ends. Dovecot calls
crypt inside mycrypt. While in mycrypt, the poi
Hi,
The link to the release notes seems should have an 'l' on the end:
Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html
This with gdb:
thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb
/root/dovecot-auth-crash/auth /root/dovecot-auth-crash/core.auth.29667
GNU gdb (G
Hi!
Thank you for the report, few points though:
- The link you provided is broken
- getting glibc-2.28 prebuilt seems to be bit problematic, and what I
read from their changelog, the crypt function should work as normal.
That said, it would be somewhat helpful if you could use gdb to find out
