From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15724 invoked by alias); 19 Nov 2002 11:06:46 -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 15717 invoked from network); 19 Nov 2002 11:06:45 -0000 Received: from unknown (HELO cerbere.u-strasbg.fr) (130.79.112.250) by sources.redhat.com with SMTP; 19 Nov 2002 11:06:45 -0000 Received: from laocoon.ics.u-strasbg.fr (laocoon.u-strasbg.fr [130.79.112.72]) by cerbere.u-strasbg.fr (Postfix) with ESMTP id D7BAC4C6; Tue, 19 Nov 2002 12:22:12 +0100 (CET) Message-Id: <5.0.2.1.2.20021119120149.02afde90@ics.u-strasbg.fr> X-Sender: muller@ics.u-strasbg.fr Date: Tue, 19 Nov 2002 03:06:00 -0000 To: Jim Blandy , Michael Snyder From: Pierre Muller Subject: Re: [RFC] Display exact entered expression for watchpoints Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com In-Reply-To: <20021114195320.GA3094@nevyn.them.org> References: <5.0.2.1.2.20021114112441.032c9fb0@ics.u-strasbg.fr> <5.0.2.1.2.20021114112441.032c9fb0@ics.u-strasbg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2002-11/txt/msg00486.txt.bz2 At 20:53 14/11/2002, Daniel Jacobowitz wrote: >On Thu, Nov 14, 2002 at 12:00:18PM +0100, Pierre Muller wrote: >> When I watch a memory location, >> I almost always use hexadecimal notation. >> >> For instance lets say that I want to watch >> the memory containing the value of gdb_stderr >> On my linux box >> (top-gdb)p &gdb_stderr >> returns >> $1 = (struct ui_file **) 0x823b5cc >> (ok, here I could simply use 'watch gdb_stderr, >> but in some other cases like dynamically allocated memory I can't). >> if I enter >> (top-gdb) watch *0x823b5cc >> Hardware watchpoint 3: *136558028 >> (top-gdb) inf b >> Num Type Disp Enb Address What >> 1 breakpoint keep y 0x080f0d79 in internal_error >> at ../../src/origdb/utils.c:810 >> 2 breakpoint keep y 0x080783eb in info_command >> at ../../src/origdb/cli/cli-cmds.c:202 >> silent >> return >> 3 hw watchpoint keep y *136558028 >> (top-gdb) >> >> >> After my patch, I get >> (top-gdb) watch *0x823b5cc >> Hardware watchpoint 3: *0x823b5cc >> (top-gdb) inf b >> Num Type Disp Enb Address What >> 1 breakpoint keep y 0x080f0d79 in internal_error >> at ../../src/origdb/utils.c:810 >> 2 breakpoint keep y 0x080783eb in info_command >> at ../../src/origdb/cli/cli-cmds.c:202 >> silent >> return >> 3 hw watchpoint keep y *0x823b5cc >> >> >> I really prefer the later, > > >I like this behavior a lot better too; I see the number and get >hopelessly confused as to what I'm watching :) Michael, Jim, do you >think this will cause any problems? Watch doesn't take an implicit >argument the way that break does, so a string should always be >available. So, I think that after looking into the MAINTAINERS file, I need approval from either Jim Blandy or Michael Snyder on this RFC. Original RFC is http://sources.redhat.com/ml/gdb-patches/2002-11/msg00409.html