From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10941 invoked by alias); 26 Nov 2003 14:37:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10932 invoked from network); 26 Nov 2003 14:37:57 -0000 Received: from unknown (HELO localhost.redhat.com) (65.49.0.121) by sources.redhat.com with SMTP; 26 Nov 2003 14:37:57 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 7C7092B8F; Wed, 26 Nov 2003 09:37:53 -0500 (EST) Message-ID: <3FC4BAC1.7040906@gnu.org> Date: Wed, 26 Nov 2003 14:37:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J. Johnston" Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [WIP] pending breakpoint support References: <3FBAC14D.4060002@redhat.com> <20031119150659.GA14955@nevyn.them.org> <3FBBFD90.8080106@redhat.com> <3FBE95D3.4000300@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00592.txt.bz2 > I tried leaving the breakpoint around to allow for "break in all shared libs" but that experiment fell flat because it ended up creating the same breakpoint multiple times as each shared library gets loaded (e.g. it keeps finding printf over and over again in libc). This patch still finds the first occurrence in a shared library and then deletes the pending breakpoint. Are there plans to identify the shared library for a breakpoint in the proposed changes? That sounds reasonable for the first cut (who would do that anyway). Get the underlying mechanism working right, and then start to work out the human-computer-interface issues. It's really part of that regex breakpoints, breakpoint groups type problem and can be addressed in a later pass - once we've got more experience with the problem. File some bug reports :-) Andrew