From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8630 invoked by alias); 19 Dec 2002 09:16:26 -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 8616 invoked from network); 19 Dec 2002 09:16:24 -0000 Received: from unknown (HELO postfix2.ofir.com) (193.0.243.237) by 209.249.29.67 with SMTP; 19 Dec 2002 09:16:24 -0000 Received: from webmail5.ofir.dk (unknown [192.168.197.25]) by postfix2.ofir.com (Postfix) with ESMTP id B1FDB342DA for ; Thu, 19 Dec 2002 10:47:01 +0100 (CET) X-WM-Posted-At: webmail5.ofir.dk; Thu, 19 Dec 02 10:16:11 +0100 Date: Thu, 19 Dec 2002 01:16:00 -0000 From: James Sampson To: GDB Archive X-EXP32-SerialNo: 00002117 Subject: RE: Debugging GDB and breaking? Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20021219094701.B1FDB342DA@postfix2.ofir.com> X-SW-Source: 2002-12/txt/msg00286.txt.bz2 >Some general hints for debugging gdb: Cool! >I start with "gdb /my/gdb/to/debug/bin/gdb". I like to use a stable gdb >for the top gdb, such as the vendor-supplied gdb or gdb 5.3. Also this >helps separate, in my mind, the top gdb from the inferior gdb. I didn't even know the 5.3 was out - Gonna grab that immediatly :-) >After that, in your specific case, you want to break at break_command >and then use "next" and "step" from there. Ok, so the "break_command" is the first function to be called when setting a breakpoint? :-) >Hope this helps, Sure did, thanks :-D Best Regards James