Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: ghost@cs.msu.su, gdb-patches@sources.redhat.com
Subject: Re: Variable identification (Was: [RFA] Don't reset watchpoint 	block on solib load.)
Date: Fri, 30 Nov 2007 20:53:00 -0000	[thread overview]
Message-ID: <uk5nz1mmy.fsf@gnu.org> (raw)
In-Reply-To: <1196384986.2501.141.camel@localhost.localdomain> (message from 	Michael Snyder on Thu, 29 Nov 2007 17:09:46 -0800)

> From: Michael Snyder <msnyder@specifix.com>
> Cc: gdb-patches@sources.redhat.com
> Date: Thu, 29 Nov 2007 17:09:46 -0800
> 
> I haven't followed the discussion closely, but
> shouldn't it be up to the GUI to keep such persistant
> info?  It's nothing to do with gdb, really.  It's the
> GUI's state.

I'm not sure what you are talking about.  This discussion mentioned
two different aspects of watchpoints: I wanted the watchpoints on
automatic variables defined in `main' to not be deleted when the
program exits, and Vlad was talking about automatic variables in
general (which hits the problem with recursive invocations of the same
function).  I submit that the former is how GDB should behave, and
that the fact it doesn't today is a misfeature, unrelated to the GUI
state.  To a programmer, automatic variables in `main' are almost
indistinguishable from static variables, so watchpoints on both kinds
should behave the same.


  parent reply	other threads:[~2007-11-30 20:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 17:14 [RFA] Don't reset watchpoint block on solib load Vladimir Prus
2007-11-27 23:00 ` Jim Blandy
2007-11-28 15:59   ` Vladimir Prus
2007-11-28 16:23     ` Vladimir Prus
2007-11-28 19:46     ` Jim Blandy
2007-11-28 20:04       ` Vladimir Prus
2007-11-28 22:37         ` Jim Blandy
2007-11-29  6:09           ` Vladimir Prus
2007-11-28 22:50         ` Jim Blandy
2007-11-28 22:18     ` Jim Blandy
2007-11-29  4:24       ` Eli Zaretskii
2007-11-29  7:04         ` Vladimir Prus
2007-11-29 18:54           ` Jim Blandy
2007-11-29 19:03             ` Variable identification (Was: [RFA] Don't reset watchpoint block on solib load.) Vladimir Prus
2007-11-30  1:22               ` Michael Snyder
2007-11-30  5:52                 ` Vladimir Prus
2007-11-30 20:53                 ` Eli Zaretskii [this message]
2007-12-01  1:39                 ` Variable identification Jim Blandy
2007-12-01  1:47                   ` Michael Snyder
2008-01-16  1:29     ` [RFA] Don't reset watchpoint block on solib load Jim Blandy
2008-01-23  9:58       ` Vladimir Prus
2008-01-29 15:23         ` Daniel Jacobowitz
2007-11-29  6:55   ` Vladimir Prus
2007-11-29 18:40     ` Jim Blandy
2007-11-29 18:45       ` Vladimir Prus

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=uk5nz1mmy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=msnyder@specifix.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