Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Jim Blandy <jimb@redhat.com>, Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Display exact entered expression for watchpoints
Date: Tue, 19 Nov 2002 03:06:00 -0000	[thread overview]
Message-ID: <5.0.2.1.2.20021119120149.02afde90@ics.u-strasbg.fr> (raw)
In-Reply-To: <20021114195320.GA3094@nevyn.them.org>

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





  reply	other threads:[~2002-11-19 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  3:01 Pierre Muller
2002-11-14 11:52 ` Daniel Jacobowitz
2002-11-19  3:06   ` Pierre Muller [this message]
2002-11-14 17:58 ` Duncan Roe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.0.2.1.2.20021119120149.02afde90@ics.u-strasbg.fr \
    --to=muller@ics.u-strasbg.fr \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=msnyder@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox