>>>>> "NM" == Nicolas Mailhot <[email protected]> writes:

NM> BTW dovecot is broken by all the compiler and crypto changes, both
NM> for the two last rebuilds (that failed) and the build before (that
NM> succeeded but has broken auth which is sort of needed for an imap
NM> server)

Interestingly enough, cyrus-imapd is also broken.  Technically it
compiles fine and mostly runs fine, but the extensive test suite (which
we now run at build time) causes the xapian-based search indexing
component to segfault deep down in the bowels of some tests.

In what is surely a plan to make me lose the rest of my hair, the
failures _only_ happen when run in mock.  In a clean rawhide VM or
docker container with enough build deps to run fedpkg local, things
build fine.  So far the only thing resembling a backtrace I've been able
to get out of anything is just this which coredumpctl saves:

    #0  0x0000000000000120 n/a (n/a)
    #1  0x00007ffd8745b720 n/a (n/a)
    #2  0x00007fb063abac80 
_ZTVNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE (libstdc++.so.6)

That makes me wonder if I'm hitting a libstdc++ bug.  If I do
coredumpctl gdb and then to a backtrace, I just get:

(gdb) bt
#0  0x0000000000000120 in ?? ()
#1  0x00007fb06352881e in ?? ()
#2  0x00007ffd8745b7b0 in ?? ()
#3  0x00007ffd8745b528 in ?? ()
#4  0x0000000000000000 in ?? ()

which obviously isn't helpful.  And this was obtained by running mock on
a rawhide VM where I've made sure that the environment inside and
outside of the chroot have the same packages, all debuginfo is installed
and the test suite is run in %install instead of %check so that the
unstripped binaries are executed.  I can't figure out a way to get more
useful information out.

 - J<
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to