From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26478 invoked by alias); 7 Dec 2007 14:01:51 -0000 Received: (qmail 26461 invoked by uid 22791); 7 Dec 2007 14:01:50 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Dec 2007 14:01:43 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J0dlW-000150-JZ for gdb-patches@sources.redhat.com; Fri, 07 Dec 2007 14:01:18 +0000 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Dec 2007 14:01:18 +0000 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Dec 2007 14:01:18 +0000 To: gdb-patches@sources.redhat.com From: Vladimir Prus Subject: Re: Debugging a Vlc dll with GDB. Date: Fri, 07 Dec 2007 14:09:00 -0000 Message-ID: References: <20071206182343.GA16137@caradoc.them.org> <433908.24398.qm@web57701.mail.re3.yahoo.com> <20071206202850.GA27429@caradoc.them.org> <47586224.CE80C330@dessent.net> <475893BA.8000700@portugalmail.pt> <20071207004226.GA30430@caradoc.them.org> <4758A871.9060508@portugalmail.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.4 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00124.txt.bz2 Pedro Alves wrote: > Daniel Jacobowitz wrote: >> On Fri, Dec 07, 2007 at 12:28:42AM +0000, Pedro Alves wrote: >>> I could swear there use to be a "pending resolved" >>> notice. Did it go away with the multiple breakpoint >>> location support? >> >> Yes, I believe so. It was mostly there to warn you that the >> breakpoint number had changed, which Vladimir has now fixed. >> > > Humm, I found it useful, as in "ok, the breakpoint I set in a > function that will only trigger after I do this, that, and that, > is correctly set". Now, I have to interrupt the inferior and > do an info breakpoints to see if it got in. Well, in MI any change of breakpoint should result in a notification -- though it does not do now. I have no idea whatsoever what should CLI do, but it seems to be strange that you have to regularly check if your breakpoint is set -- is GDB *that* buggy? - Volodya