When trying to emerge evolution-data-server 1.0.0 on an amd64 machine, the build crashes during lock file tests in libical component. Seems amd64 related as it merged on a x86. You'll find attached the emerge log file and the emerge --info output. Here are the flags used to build: gnome-extra/evolution-data-server-1.0.0 -debug +doc +ldap Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 41479 [details] emerge --info output
Created attachment 41480 [details] emerge logfile
Still crashes the same way with evolution-data-server-1.0.2.
are you able to manually go into the directory and get a core dump for make test? use: ulimit -c unlimited
Can't attach the core dump, as it's too big and is rejected. If I go into the /var/tmp/portage/evolution-data-server-1.0.2/work/evolution-data-server-1.0.2/calendar/libical/src/test directory and launch regression by hand, file lock test is succesfull and I got another crash: [...] ########## Test File Locks (22) ########## .................................................. Final: 101 ########## Test X Props and Params (23) ########## ok 464 - icalparser_parse_string() ok 465 - get RRULE property ########## Test Trigger (24) ########## ok 466 - icalparser_parse_string() ok 467 - parsed triggers ok 468 - TRIGGER;VALUE=DATE-TIME:19970101T120000 ok 469 - TRIGGER;VALUE=DURATION:P3DT3H50M45S ok 470 - TRIGGER;VALUE=DATE-TIME:19970101T120000 ok 471 - TRIGGER;VALUE=DURATION:P3DT3H50M45S ok 472 - TRIGGER;VALUE=DATE-TIME:19970101T120000 ok 473 - TRIGGER;VALUE=DURATION:P3DT3H50M45S ok 474 - TRIGGER;VALUE=DATE-TIME:19970101T120000 ok 475 - TRIGGER;VALUE=DURATION:P3DT3H50M45S ########## Test Restriction (25) ########## Segmentation fault (core dumped) it seems that it crashes exactly at the same place in the two cases. I'll attach infos I got with gdb. Please tell me if you need more.
Created attachment 42039 [details] infos I got from gdb when regression test crashes during file lock test.
Created attachment 42040 [details] infos I got from gdb when regression test crashes during restriction test
We just don't have the time for this I'm afraid. *** This bug has been marked as a duplicate of 69343 ***