From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16722 invoked by alias); 23 Jul 2004 20:44:47 -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 16712 invoked from network); 23 Jul 2004 20:44:46 -0000 Received: from unknown (HELO hall.mail.mindspring.net) (207.69.200.60) by sourceware.org with SMTP; 23 Jul 2004 20:44:46 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by hall.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bo6uM-0005ui-00; Fri, 23 Jul 2004 16:44:46 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id B4ADA4B102; Fri, 23 Jul 2004 16:45:30 -0400 (EDT) Date: Sat, 24 Jul 2004 07:53:00 -0000 From: mec.gnu@mindspring.com To: lsr@vinci.inesc-id.pt Subject: Re: gdb calls bypassbreakpoints Cc: gdb@sources.redhat.com Message-ID: <410178E9.nail3NY14VXRW@mindspring.com> References: In-Reply-To: User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00305.txt.bz2 > Is there a way to stop this behavior and make gdb act as if the call > had came from the C file? Well, no. When gdb hits a breakpoint in your program, it has to discard the state information and just get back to the top level of the interpreter. That is, if you do this: (gdb) break foo (gdb) break bar (gdb) print foo() + bar() Then when gdb hits the breakpoint in foo(), it's going to forget that it was in the middle of evaluating "foo() + bar()". gdb will continue evaluating foo(), and when that is done, gdb will ask for more commands and not continue with the "+ bar()" part. Michael C GDB QA Guy