From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16714 invoked by alias); 21 Sep 2004 10:43:38 -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 16701 invoked from network); 21 Sep 2004 10:43:36 -0000 Received: from unknown (HELO alice.acmet.com) (61.16.238.202) by sourceware.org with SMTP; 21 Sep 2004 10:43:36 -0000 Received: from monika (localhost [127.0.0.1]) by alice.acmet.com (8.11.6/8.11.6) with ESMTP id i8LApFb13440; Tue, 21 Sep 2004 16:21:15 +0530 From: "Monika Chaddha" To: "'Schneider, Jan \(GE51\)'" Cc: , Subject: RE: debugging the gdb with itself Date: Tue, 21 Sep 2004 10:43:00 -0000 Message-ID: <006601c49fc7$c9ea99c0$5100a8c0@monika> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <938F1554888BD71194E100B0D0FCD97201AAD7C1@ge51smail2.ge51.honeywell.de> X-SW-Source: 2004-09/txt/msg00167.txt.bz2 Pls follow the following steps 1. Invoke DDD "$ ddd " 2. Pls set the option from the menu in DDD. "Program => Run in Execution window" 3. Set the breakpoints in the source if need 4. Now run 5. After running the execution window will appear. This execution window is the input console for the GDB which is debugging. The GDB console in DDD will not be overlap by the gdb (which is debugging). Pls try this. It should work. Monika >-----Original Message----- >From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com] On >Behalf Of Schneider, Jan (GE51) >Sent: Tuesday, September 21, 2004 2:51 PM >To: 'gdb@sources.redhat.com' >Subject: debugging the gdb with itself > >Hi, > >I want to debug the gdb using the ddd. I have read the capter "debugging >gdb >with itself" and I have googled >on that topic, but I didn't get alot of infos. >I have copied the gdb to gdb2 and started the gdb2. Then I started the ddd >with an attach at the gdb2. >But then I can't walk through the gdb sources. >Is there another way debugging the gdb using ddd? > >Thanks