From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4797 invoked by alias); 19 Oct 2006 19:56:08 -0000 Received: (qmail 4786 invoked by uid 22791); 19 Oct 2006 19:56:07 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 19 Oct 2006 19:56:02 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Gadzj-0008Gj-Dx; Thu, 19 Oct 2006 15:55:59 -0400 Date: Thu, 19 Oct 2006 19:56:00 -0000 From: Daniel Jacobowitz To: "Joshua D. Boyd" Cc: gdb@sourceware.org Subject: Re: Weird debugging problem Message-ID: <20061019195559.GA31741@nevyn.them.org> Mail-Followup-To: "Joshua D. Boyd" , gdb@sourceware.org References: <1161287368.2428.43.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1161287368.2428.43.camel@localhost.localdomain> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00142.txt.bz2 On Thu, Oct 19, 2006 at 03:49:28PM -0400, Joshua D. Boyd wrote: > When I run the program in gdb, eventually (usually after running for 12+ > hours), I get the following: > [New Thread -1734661200 (LWP 67296)] > Can't attach LWP 67296: No such process > (gdb) > Now, if I'm not mistaken, that is not a valid process ID for Linux or > most other Unix type operating systems. > > If I do a back trace at that point, it reports the current thread is the > main parent, which is currently in a nanosleep (and that thread's normal > behavior after start-up is to sleep most of the time and do house > keeping tasks when it wakes up). > > At this point I am at a complete loss about what could be happening or > what to try next, so after scanning through archives and a short period > of lurking, I decided to hope that someone here could provide some > advice. The error itself is fairly common and can have many causes, but I admit the >32k PID is odd and suggests that something different is happening here. I'm afraid I can't offer you much advice. When this happens, you might want to check which threads actually exist, by looking in /proc/PID/task. -- Daniel Jacobowitz CodeSourcery