From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11491 invoked by alias); 21 Aug 2002 19:11:37 -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 11484 invoked from network); 21 Aug 2002 19:11:36 -0000 Received: from unknown (HELO web11201.mail.yahoo.com) (216.136.131.171) by sources.redhat.com with SMTP; 21 Aug 2002 19:11:36 -0000 Message-ID: <20020821191135.1896.qmail@web11201.mail.yahoo.com> Received: from [192.55.52.2] by web11201.mail.yahoo.com via HTTP; Wed, 21 Aug 2002 12:11:35 PDT Date: Wed, 21 Aug 2002 12:11:00 -0000 From: Datoda Subject: Debugging a process that does fork on Intel Linux To: gdb@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00254.txt.bz2 Hi, GDB has the concept of a catchpoint to catch a fork syscall in the debuggee. Alas, it doesn't work (yet) on intel linux. I put a little thought in it and thinks that what's missing is a kernel support for putting the parent and the child processes in a stopped state when the fork syscall is complete. At that point, the debugger can then attach to the child process and bring it under control. I was wondering if such a kernel support exists? If not, is there a plan for adding it? Or are there other ideas for catching forks on Linux? TIA. __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com