[Sorry, the mail was intended to be Cc:ed to the list]
---------- Forwarded message ---------- From: Francis Galiegue <[email protected]> Date: 2009/10/12 Subject: Re: [Qt-jambi-interest] Help needed: generator debugging (SIGSEGV on run) To: José Arcángel Salazar Delgado <[email protected]> 2009/10/12 José Arcángel Salazar Delgado <[email protected]>: [...] > Today I tried to build qt jambi community 4.6. It didnt send a segfault, but > I was unable to build it for some unknow reason. > Well, yes it did: > /home/arcangel/qtjambi-unstable/community-port-to-4_6/generator/generator > --output-directory=/home/arcangel/qtjambi-unstable/community-port-to-4_6 > /home/arcangel/qtjambi-unstable/community-port-to-4_6/generator/qtjambi_masterinclude.h > /home/arcangel/qtjambi-unstable/community-port-to-4_6/generator/build_all.txt > failed with exit code: 139 > 139 == 128 + 11, meaning the program was interrupted by a signal (128), and signal 11 == SIGSEGV :p So, you have the same problem as I have. And you have a segfault at exactly the same point as me! I compiled a debug build, did ulimit -c 0 and could obtain a core, tried to debug it but couldn't go very far. -- Francis Galiegue, [email protected] "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) -- Francis Galiegue, [email protected] "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
