From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21455 invoked by alias); 2 Dec 2004 09:56:46 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20859 invoked from network); 2 Dec 2004 09:56:21 -0000 Received: from unknown (HELO mail.printsoft.ch) (217.193.172.19) by sourceware.org with SMTP; 2 Dec 2004 09:56:21 -0000 Received: by mail.printsoft.ch (Postfix, from userid 65534) id E40A43507E; Thu, 2 Dec 2004 10:56:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.printsoft.ch (Postfix) with ESMTP id 8481E368AE for ; Thu, 2 Dec 2004 10:56:16 +0100 (CET) Received: from toe.printsoft-intern.ch (inn.printsoft.ch [217.193.172.30]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by mail.printsoft.ch (Postfix) with ESMTP id 5BDD111DFC for ; Thu, 2 Dec 2004 10:56:16 +0100 (CET) From: Tobias Erbsland Organization: PrintSoft (Schweiz) AG To: gdb@sources.redhat.com Subject: Re: Threading bug, already solved, or is there a workaround? Date: Thu, 02 Dec 2004 09:56:00 -0000 User-Agent: KMail/1.7.1 References: <200412011252.47465.terbsland@printsoft.ch> <20041201171640.GA8619@nevyn.them.org> In-Reply-To: <20041201171640.GA8619@nevyn.them.org> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_/aurBpncupYAyDH" Message-Id: <200412021056.15660.terbsland@printsoft.ch> X-Virus-Scanned: by AMaViS X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on linth.printsoft.ch X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=ham version=2.64 X-SW-Source: 2004-12/txt/msg00009.txt.bz2 --Boundary-00=_/aurBpncupYAyDH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-length: 2287 Hello > > I'm currently try to debug a multithreaded application with gdb. It see= ms > > that there are this threading problems described in the PROBLEMS > > document. (It's a SuSE 9.2, but i installed gdb 6.3 in the hope, the bug > > is already solved.) > > > > Is there already a solution for that problem? Or is there a workaround? > > Which problem, specifically, do you mean? What symptoms do you see? If i try to debug an multithread application with gdb, the threads aren't=20 started. Without gdb all is working fine. An minimal example program for Qt with qmake. The regular output would be: **snip** drzoom@toe:~/Entwicklung/kdevelopthreadbug/bin> ./kdevelopthreadbug start 5 thread Start thread 0 Start thread 1 Start thread 2 Start thread 3 Start thread 4 Thread started Thread started Thread started Thread started Thread started Start thread 5 Start thread 6 Start thread 7 Start thread 8 Start thread 9 Thread started Thread started Thread started Thread started Thread started 5 threads are running... Thread done Thread done Thread done Thread done Thread done Thread done Thread done Thread done Thread done Thread done **snip* The output with the debugger is: drzoom@toe:~/Entwicklung/kdevelopthreadbug/bin> /usr/bin/gdb kdevelopthread= bug GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. =A0Type "show warranty" for detail= s. This GDB was configured as "i586-suse-linux"...Using host libthread_db libr= ary=20 "/lib/tls/libthread_db.so.1". (gdb) r Starting=20 program: /home/drzoom/Entwicklung/kdevelopthreadbug/bin/kdevelopthreadbug [Thread debugging using libthread_db enabled] warning: Unable to set global thread event mask: generic error [New Thread 1085896896 (LWP 6096)] start 5 thread Start thread 0 Start thread 1 Start thread 2 Start thread 3 Start thread 4 Start thread 5 Start thread 6 Start thread 7 Start thread 8 Start thread 9 5 threads are running... I tried the same with gdb 6.1, 6.2.1 and with 6.3. Everywhere the same=20 problem. The example as attachement. kind regards Tobias --Boundary-00=_/aurBpncupYAyDH Content-Type: application/x-tgz; name="bug.tar.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bug.tar.gz" Content-length: 1013 H4sIAMOyrUEAA+2W60/bMBDA+7X+K06gSeEVkvSBVB5SRzuENsaraB+2aXKT W+uROq3jtBWI/32XpNCOdgwNjQnknxTZvpzvfH6c7jLAIYZRX3cV8qCddDYv 70vsvooKT8EhquVy2rpbFScbu/k4o1x2Cq7jVkrellMplwqO55arlQI4T/L6 SJJYcwVQCNRVFPUe0kMVP2BnEstd+0JYhobAGKHBNQoYJSpA6AkNAfZg0OOX uHHEJe+ggmEk4X0jvxtAe6ExDLUNbBk2Hk+qfiE1qiGqKxR+V4oYFIZciyFc JT04UdEPvNQzv2tg06QGj6HFVQc1iFjfqoHozZtjbP/447vDA1jbTU0jp/C+ MLhjxJX8RsGwVvPo5EO91YRdiJN2IBTNPb942zg8O0/nxsoH9r/P518z99o3 KewFOcDv9//axx/ev+t4pfz9l1yvWknfv+eVSub9PweMLQvphwk9+50B7/dD 4dNbjKTd3Zv9k1+EVMj8kMcxfOJCtzIh1KCftGkenOYCds1yQY0Vh0LphIeU PEQAKpHWCites2Jx0EC6VRYsTWykh6AxWIKVbfobh4h9C1wnH95XDiKJE00c C22lvRvGimRE0zIyX+PcxsTdrUHIVW+2GRNSQ48LaaUdSiz+Ovhdugmr1B9+ /rpCURRP69MNAdoca6KYqmSmpruwCiNKIw4Zni43CwoqkG9evuLvkbIgdTnO 1KnZoTipXVuD+3tzns3PZ8ObYGmdtLOoU1cSRzOHYOXyjb3M52RHppZu1xDT 0jE9Bylkx7btbE2sSKHZOEY/nXfz6lOeYYbF+Z++J1d9U/5U/1Udb1r/eVsF 0iqVqyb/Pwcvov5L7+N8DYhCItTlCGWQyE4NwLY320LOFy+MtepnB80WZc3f qcBMzRikSXNhxTgrG+hfhpMsPVtTUlalevL44my/mdWTC4uq119hGgwGg8Fg MBgMBoPBYDAYDAaDwWAwGJ6Tnzsq/aMAKAAA --Boundary-00=_/aurBpncupYAyDH--