From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3491 invoked by alias); 6 Dec 2004 15:59:39 -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 3464 invoked from network); 6 Dec 2004 15:59:34 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 6 Dec 2004 15:59:34 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CbLGs-0004Rz-03; Mon, 06 Dec 2004 10:59:30 -0500 Date: Mon, 06 Dec 2004 15:59:00 -0000 From: Daniel Jacobowitz To: Tobias Erbsland Cc: gdb@sources.redhat.com Subject: Re: Threading bug, already solved, or is there a workaround? Message-ID: <20041206155929.GA16718@nevyn.them.org> Mail-Followup-To: Tobias Erbsland , gdb@sources.redhat.com References: <200412011252.47465.terbsland@printsoft.ch> <20041201171640.GA8619@nevyn.them.org> <200412021056.15660.terbsland@printsoft.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412021056.15660.terbsland@printsoft.ch> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-12/txt/msg00025.txt.bz2 On Thu, Dec 02, 2004 at 10:56:15AM +0100, Tobias Erbsland wrote: > > Hello > > > > I'm currently try to debug a multithreaded application with gdb. It seems > > > 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 > started. Without gdb all is working fine. > > An minimal example program for Qt with qmake. > > The regular output would be: Your test works for me on Debian unstable. I can only assume that SuSE has some change in glibc, libqt, or the kernel that caused this problem; you may want to take it up with SuSE. -- Daniel Jacobowitz