From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17539 invoked by alias); 28 Jan 2003 15:47:07 -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 17522 invoked from network); 28 Jan 2003 15:47:07 -0000 Received: from unknown (HELO linux) (24.209.209.134) by 172.16.49.205 with SMTP; 28 Jan 2003 15:47:07 -0000 Received: from bdill by linux with local (Exim 3.35 #1 (Debian)) id 18dXy8-0003Tt-00; Tue, 28 Jan 2003 10:48:12 -0500 Date: Tue, 28 Jan 2003 15:47:00 -0000 To: Markus Werle Cc: gdb@sources.redhat.com Subject: Re: catch throw -how? Message-ID: <20030128154812.GA13362@linux.dillfamily.org> References: <3E36A332.9648D75E@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E36A332.9648D75E@web.de> User-Agent: Mutt/1.3.28i From: "Bennett F. Dill" X-SW-Source: 2003-01/txt/msg00462.txt.bz2 On Tue, Jan 28, 2003 at 04:35:14PM +0100, Markus Werle wrote: > Hi! > > Using gdb-5.1.1 I wanted to use the "catch" feature for C++ exceptions like this > > # gdb ./myprogram > GNU gdb 5.1.1 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i686-pc-linux-gnu"... > (gdb) catch throw > You can't do that without a process to debug. > (gdb) > > 1. I do not understand the error message, please explain > 2. Is this a bug resolved in gdb-5.3 or am I missing some information? > > > best regards, > > > Markus > Markus, I'm not sure, but i think you may need to specify a core file at startup, or attach to a process that you want to debug... process id of program to debug = 4128 user@host:~$ gdb (gdb) attach 4128 Attaching to process 4128 Reading symbols from /usr/lib/libcurses.so.1...(no debugging symbols found)... done. Reading symbols from /usr/lib/libc.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libdl.so.1...(no debugging symbols found)...done. Reading symbols from /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1... (no debugging symbols found)...done. Symbols already loaded for /usr/lib/libcurses.so.1 Symbols already loaded for /usr/lib/libc.so.1 Symbols already loaded for /usr/lib/libdl.so.1 Symbols already loaded for /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1 0xff319ad4 in syscall () from /usr/lib/libc.so.1 (gdb) now try your catch... I'm not sure if that helps or not, but good luck :-) Ben