From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21004 invoked by alias); 15 Mar 2006 16:30:01 -0000 Received: (qmail 20955 invoked by uid 22791); 15 Mar 2006 16:30:00 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 15 Mar 2006 16:29:57 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.50) id 1FJYse-0005Gh-7d for gdb@sources.redhat.com; Wed, 15 Mar 2006 19:29:53 +0300 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by zigzag.lvk.cs.msu.su with esmtp (Exim 4.50) id 1FJYsO-0005De-Kt; Wed, 15 Mar 2006 19:29:32 +0300 From: Vladimir Prus To: Jim Ingham Subject: Re: MI and pending breakpoints Date: Wed, 15 Mar 2006 16:31:00 -0000 User-Agent: KMail/1.7.2 Cc: gdb@sources.redhat.com References: <27491BE6-9DDB-4168-BDFC-9C092BF0DEBB@apple.com> In-Reply-To: <27491BE6-9DDB-4168-BDFC-9C092BF0DEBB@apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603151929.31842.ghost@cs.msu.su> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00080.txt.bz2 On Wednesday 15 March 2006 19:19, Jim Ingham wrote: > You need to set the gdb variable "pending" to "on" before setting the > breakpoint. Do you mean: set breakpoint pending on ? That's what I do (not shown in the example), and without it the ordinary "break" won't set the breakpoint -- it will ask if pending breakpoint should be set. But even with it, "-break-insert" refused to set pending breakpoint. Maybe, there's was bug that's fixed on Apple branch? In fact, with CVS HEAD version, -break-insert calls gdb_breakpoint, which calls do_captured_parse_breakpoint which reports that file does not exists, and process stops (see breakpoint.c:gdb_breakpoint and mi/mi-cmd-break.c:mi_cmd_break_insert). For "break", the do_captures_parse_breakpoint" is called as well, but after then, an explicit check for not found file is made, and pending breakpoint is added (see breakpoint.c:break_command_1) > Since this is kind of a pain, we added a "-f" option to - > break-insert that will do this for you wrapped around the breakpoint > setting ("-f" because this feature was called "future-break" in the > NeXT gdb many years ago.) > > It's also arguable that for -break-insert you ALWAYS want "pending" > to be "on". Yes, this might be good. - Volodya