Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Checking if addess is on stack?
Date: Thu, 20 Apr 2006 11:42:00 -0000	[thread overview]
Message-ID: <uejzswnqq.fsf@gnu.org> (raw)
In-Reply-To: <e27hvh$a2l$1@sea.gmane.org> (message from Vladimir Prus on Thu, 	20 Apr 2006 12:49:53 +0400)

> From:  Vladimir Prus <ghost@cs.msu.su>
> Date:  Thu, 20 Apr 2006 12:49:53 +0400
> 
> in order to improve watchpoints handling in KDevelop, I need to figure out
> if a given address is part of current frame's stack. Is there any command
> to produce that information? I guess I can look at frame base address and
> check if my address is "close" to that, but it's a bit unreliable.
> 
> For reference, the watchpoint changes for KDevelop are outlined at:
> 
>   http://lists.kde.org/?l=kdevelop-devel&m=114552206721831&w=2

I think one way to solve the problems you describe in that URL is to
set a temporary breakpoint whose commands set the watchpoint:

   tb do_that
   commands
   > watch ptr->i
   > continue
   > end

(and similarly for block-local variables: put a breakpoint on the
block's first line).  If you want to keep the watchpoints between
sessions, record the temporary breakpoints and reinsert them when the
session starts.

Would this do what you want?


  reply	other threads:[~2006-04-20 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 10:27 Vladimir Prus
2006-04-20 11:42 ` Eli Zaretskii [this message]
2006-04-20 11:48   ` Vladimir Prus
2006-04-20 12:21     ` Eli Zaretskii
2006-04-20 12:49       ` Vladimir Prus
2006-04-20 14:27         ` Eli Zaretskii
2006-04-20 14:39           ` Daniel Jacobowitz
2006-04-20 15:24             ` Eli Zaretskii
2006-04-20 15:32               ` Daniel Jacobowitz
2006-04-20 18:41                 ` Eli Zaretskii
2006-04-20 19:12                   ` Daniel Jacobowitz
2006-04-21 11:45                     ` Eli Zaretskii
2006-04-22  8:06                       ` Daniel Jacobowitz
2006-04-20 16:29           ` Vladimir Prus
2006-04-20 19:03             ` Eli Zaretskii

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