From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 577 invoked by alias); 26 Jul 2004 21:19:54 -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 566 invoked from network); 26 Jul 2004 21:19:53 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 26 Jul 2004 21:19:53 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i6QLJre3004240 for ; Mon, 26 Jul 2004 17:19:53 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i6QLJqa03475; Mon, 26 Jul 2004 17:19:52 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0739E2B9D; Mon, 26 Jul 2004 17:19:49 -0400 (EDT) Message-ID: <41057574.6010005@gnu.org> Date: Mon, 26 Jul 2004 21:21:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Lu=EDs_Russo?= Cc: gdb@sources.redhat.com Subject: Re: gdb calls bypassbreakpoints References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2004-07/txt/msg00332.txt.bz2 > Hi, Are you asking that, for the period of the inferior function call, all the user breakpoints be disabled? yes that could be useful Andrew > I am debugging a C file. I set some breakpoints inside my C functions that print what's going on. The breakpoints have a list of commands that do some prints and some continues. > > Sometimes I want to call the functions with different arguments from those hardcoded in C, and I use the call function. > > But then I get this message: > > The program being debugged stopped while in a function called from GDB. > When the function (minSphere) is done executing, GDB will silently > stop (instead of continuing to evaluate the expression containing > the function call) > > Is there a way to stop this behavior and make gdb act as if the call had came from the C file? > > Thanks, > > Luís Russo