From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5811 invoked by alias); 17 Oct 2003 16:55:37 -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 5797 invoked from network); 17 Oct 2003 16:55:36 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 17 Oct 2003 16:55:36 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id h9HGtZk0024426 for ; Fri, 17 Oct 2003 09:55:35 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Fri, 17 Oct 2003 09:55:05 -0700 Received: from [17.201.22.245] (inghji6.apple.com [17.201.22.245]) by scv2.apple.com (8.12.9/8.12.9) with ESMTP id h9HGtKWI021717; Fri, 17 Oct 2003 09:55:20 -0700 (PDT) In-Reply-To: <8011-Fri17Oct2003085924+0200-eliz@elta.co.il> References: <1066321046.18949.ezmlm@sources.redhat.com> <631CE16C-000B-11D8-BB88-000A958F4C44@apple.com> <8011-Fri17Oct2003085924+0200-eliz@elta.co.il> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: gdb-patches@sources.redhat.com From: Jim Ingham Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] Date: Fri, 17 Oct 2003 16:55:00 -0000 To: Eli Zaretskii X-SW-Source: 2003-10/txt/msg00589.txt.bz2 Yeah, but if I told gdb to set breakpoints at *0x....., and sometimes those breakpoints would just stick at that address, and other times they would move around, that would be disconcerting to me. If the breakpoint is not going to be at a fixed address, we oughtn't to refer to it as if it were. Jim On Oct 16, 2003, at 11:59 PM, Eli Zaretskii wrote: >> From: Jim Ingham >> Date: Thu, 16 Oct 2003 12:03:11 -0700 >> >> I would be careful to stay away from turning "logically" specified >> breakpoints (by which I mean specified on function name or source >> location) into addresses to the user. Even between rerunnings of the >> same executable a library's load address can shift, causing the >> address >> to move. gdb can probably still make the equivalency between the >> breakpoints - most slides are rigid, for instance. But the address >> doesn't show this. > > I didn't say that GDB should _store_ the address that the user types > in order to disambiguate the place where to put the trap. It is just > a means to tell GDB which of the possibilities to take. It has an > advantage of being natural to GDB users, since you can put a > breakpoint on a specific address in current versions of GDB. > > After the trap was put, if GDB can solve the problem of moving > addresses (as it does that now), it can also solve the problem we are > discussing here. > -- Jim Ingham jingham@apple.com Developer Tools Apple Computer