From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30133 invoked by alias); 4 Feb 2002 09:32:06 -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 29832 invoked from network); 4 Feb 2002 09:32:00 -0000 Received: from unknown (HELO beta.dmz-eu.st.com) (164.129.1.35) by sources.redhat.com with SMTP; 4 Feb 2002 09:32:00 -0000 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with SMTP id 71FC8498D for ; Mon, 4 Feb 2002 09:31:56 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 0) id B20CE6152; Mon, 4 Feb 2002 09:32:48 +0000 (GMT) Received: from eux220.sgp.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 41AEE184A for ; Mon, 4 Feb 2002 09:32:48 +0000 (GMT) Received: from crx316.cro.st.com (crx316.cro.st.com [164.129.43.128]) by eux220.sgp.st.com (8.9.3 (PHNE_24419)/8.8.6) with ESMTP id KAA22214; Mon, 4 Feb 2002 10:31:54 +0100 (MET) Received: from dais.cro.st.com (crx722.cro.st.com [164.129.44.222]) by crx316.cro.st.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id KAA25948; Mon, 4 Feb 2002 10:33:44 +0100 (MET) Received: from st.com (crx1009 [164.129.46.109]) by dais.cro.st.com (8.8.8+Sun/8.8.8) with ESMTP id KAA23301; Mon, 4 Feb 2002 10:34:10 +0100 (MET) Message-ID: <3C5E5591.7D6F73F8@st.com> Date: Mon, 04 Feb 2002 01:32:00 -0000 From: Christophe PLANAT Organization: ST CR&D Crolles X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: salmankhilji@hotmail.com Cc: gdb@sources.redhat.com Subject: Re: Debugging gdb with gdb References: <20020203161845.B12617@act-europe.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00073.txt.bz2 brobecker@ACT-Europe.FR wrote: > > > So the question is: How do I temporarily stop the target application in > > gdb---set a break point in the target---then continue? This is useful in > > GUI applications as well. > > FWIW, I debug GDB a bit differently: I start the inferior GDB in a > terminal. I then run another GDB, and attach it to the inferior. > The idea behind this is that I want to avoid mixing the I/O in the > inferior with the commands I'm sending to GDB. > > For the GUI lovers, GVD facilitates this, because it offers a > File->Attach menu, which will then present you with a list of process. > Click, click, click, and you're attached... > > -- > Joel FYI, I use also an other way : In the top debugger (say GDB) I set a breakpoint on the function undef_cmd_error() calls each time the user hits a wrong GDB command. So when MYGDB is running, you hit a wrong command such as qwert and the GDB top debugger will stop in undef_cmd_error(). You can then do all what you want at the top GDB level inside MYGDB code. Christophe -- ---------------------------------------------------------------------- | Christophe PLANAT | Embedded Systems Technology | | Email : Christophe.Planat@st.com | STMicroelectronics | | Phone : +33 04 76 92 68 82 | 850, rue Jean-Monnet | | Fax : +33 04 76 92 50 94 | BP 16 - 38921 Crolles - France | ----------------------------------------------------------------------