X-Spam-Check-By: sourceware.org Message-ID: <43F13FEB.5050407@users.sourceforge.net> Date: Mon, 13 Feb 2006 20:26:51 -0600 From: "Yaakov S (Cygwin Ports)" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: 1.5.19: changes have broken Qt3 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com It would appear that changes to the cygwin1.dll since 1.5.18-1 (and before the 20051207 snapshot) have broken Qt3. The relevant threads until now: http://www.cygwin.com/ml/cygwin-xfree/2005-12/msg00026.html http://www.cygwin.com/ml/cygwin-xfree/2006-02/msg00005.html The bottom line is that applications dependent on Qt threads, which worked with 1.5.18, now crash silently. This also breaks building qt3 from source, as uic is similarly affected. Interestingly, running designer-qt3 (an alias for /usr/lib/qt3/bin/designer) on 1.5.19-4 uniquely raises the following error: 17 [main] designer-qt3 1628 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Using the 20060212 snapshot dll gives similar results; in the case of designer: 12 [main] designer-qt3 808 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) 594884 [main] designer-qt3 808 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) 2157249 [main] designer-qt3 808 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Running scribus, which exits silently on 1.5.19-4, with the aforementioned snapshot also gives a similar error. Note that non-threaded Qt3 apps (e.g. qtconfig) do work with all three mentioned versions of cygwin1.dll. I would like very much to get to the bottom of this. If one of the Cygwin developers could please let me know what other information I can provide to help solve this, I'd be glad to provide it. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/