It also fails without valgrind. This time I get: Backtrace: [42] /home/xisco/libo/solver/300/ unxlngi6.pro/installation/opt/program/soffice.bin: ???+0xda1 Exited with code '-1' officeconnection.cxx:140:Assertion Test name: N12_GLOBAL__N_14TestE::test setUp() failed - equality assertion failed - Expected: 2 - Actual : 0 Failures !!! Run: 1 Failure total: 1 Failures: 1 Errors: 0 dmake: Error code 1, while making 'cpptest' I attach the output of ./g log --one-1 2011/3/25 Caolán McNamara <caolanm@redhat.com>
On Fri, 2011-03-25 at 19:06 +0100, Xisco Faulí wrote:Hello, I'm trying to build this module with valgrind ( export VALGRIND=memcheck ) and I get an error in cpptest.Without VALGRIND=memcheck do you get an error ? The crucial bit looks right at the top with "Failed to connect to pipe: and exit -1" so lets disentangle a possible "smoketest doesn't work for me" vs "smoketest in a debugging build doesn't work for me" vs "smoketest doesn't work under valgrind". There was a little bit of fiddling around with the launcher script/program over the last few days, which I think should have settled down now. Hard to tell what someone is talking about at any given time, but the last time I checked under VALGRIND yesterday or so smoketest worked fine under valgrind for me something like ./g log --oneline -1 might help there. C.
Attachment:
log
Description: Binary data