From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26935 invoked by alias); 7 Mar 2007 11:20:32 -0000 Received: (qmail 26927 invoked by uid 22791); 7 Mar 2007 11:20:31 -0000 X-Spam-Check-By: sourceware.org Received: from relay1.psi.neteu.net (HELO relay1.psi.neteu.net) (154.15.246.50) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Mar 2007 11:20:27 +0000 Received: from [212.222.53.82] (helo=gg.pruftechnik.com) by relay1.psi.neteu.net with esmtp (Exim 4.65) (envelope-from ) id 1HOuBy-0002Uh-Jk for gdb@sourceware.org; Wed, 07 Mar 2007 12:20:22 +0100 Received: from gg.pruftechnik.com (localhost [127.0.0.1]) by gg.pruftechnik.com (8.13.8/8.13.8) with ESMTP id l27BKM6h008830 for ; Wed, 7 Mar 2007 12:20:22 +0100 (CET) Received: (from localhost) by gg.pruftechnik.com (MSCAN) id 1/gg.pruftechnik.com/smtp-gw/mscan; Wed Mar 7 12:20:22 2007 To: gdb@sourceware.org Subject: Re: gdb continues when I want "next" MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Markus.Grunwald@pruftechnik.com Date: Wed, 07 Mar 2007 11:20:00 -0000 Content-Type: text/plain; charset="US-ASCII" X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00110.txt.bz2 Hello, > > 2) Conditions as above, but: Sometimes, I get this when reaching the > > breakpoint for the first time: > > > > Breakpoint 1, CPTLinearGraphic::CalculateLinLines (this=0x9251de0) > > at > > /home/gru/projects/vxp/branches/branch-0-2-10- > X/Dafit_Code/drawdevices/CPTLinearGraphic.cpp:1640 > > (gdb) n > > (gdb) n > > Detaching after fork from child process 29873. > > [Thread -1863816272 (LWP 29869) exited] > > > > Program received signal SIGTRAP, Trace/breakpoint trap. > > [Switching to Thread -1863816272 (LWP 29869)] > > 0xb7446891 in __nptl_death_event () from > > /lib/tls/i686/cmov/libpthread.so.0 > I have no idea. Part of this sounds like GDB is confused by an > excessive rate of forking and thread creation / destruction. We are using threads, of course. But I doubt there is an "excessive" rate of forking/threading ... > I don't think we will be able to help you without a testcase we can > use to reproduce your problems. Hmm, that's bad. I can't give that code away, besides its size is 340MB ... Isn't there anything that I could do myself when you give me some instructions, patches, whatever ? (Sorry for sending this twice - I just hate lotus notes.) Best regards Markus Grunwald Softwaredevelopment