From: Nick Roberts <nickrob@snap.net.nz>
To: "Frédéric Riss" <frederic.riss@gmail.com>
Cc: Denis PILAT <denis.pilat@st.com>,
Vladimir Prus <ghost@cs.msu.su>,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] varobj deletion after the binary has changed
Date: Wed, 24 Jan 2007 23:14:00 -0000 [thread overview]
Message-ID: <17847.59449.255655.56503@kahikatea.snap.net.nz> (raw)
In-Reply-To: <1169679148.5160.34.camel@funkylaptop>
> You might be true. I mentioned that because it's easy to check and there
> seems to be no matching patch description in your spec file. Anyway
> fixing that seems simple enough that we don't need to dig through 80
> RedHat patches to come up with a patch.
It's not simple for me as I'm not familiar with that part (symbol tables)
of the code yet.
> AFAIK Denis's working on a version re-evealuating (actually re-parsing)
> varobjs with no attached blocks and putting the others in some error
> state that'll return in_scope="false" at the next update. Does that seem
> reasonable?
In FC5 GDB there doesn't seem to be a problem with varobjs with no attached
blocks i.e global variables, and those which do have attached blocks i.e locals
do currently return in_scope="false", on GNU/Linux at least (maybe it has
something to do with randomisation though). Like Dennis, I think there should
be some provision for deleting the latter on restarting. With watchpoints this
happens automatically.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-01-24 23:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 12:32 Denis PILAT
2007-01-23 12:45 ` Daniel Jacobowitz
2007-01-23 12:52 ` Vladimir Prus
2007-01-23 14:49 ` Denis PILAT
2007-01-24 21:49 ` Nick Roberts
2007-01-24 22:07 ` Daniel Jacobowitz
2007-01-24 22:08 ` Frédéric Riss
2007-01-24 22:18 ` Nick Roberts
2007-01-24 22:52 ` Frédéric Riss
2007-01-24 23:14 ` Nick Roberts [this message]
2007-01-25 2:41 ` Daniel Jacobowitz
2007-01-25 20:50 ` Nick Roberts
2007-01-26 7:25 ` Denis PILAT
2007-01-23 17:20 ` Denis PILAT
2007-01-25 17:28 ` Denis PILAT
2007-01-25 22:31 ` Nick Roberts
2007-01-25 23:27 ` Daniel Jacobowitz
2007-01-29 12:39 ` Denis PILAT
2007-01-29 22:12 ` Nick Roberts
2007-01-30 8:49 ` Denis PILAT
2007-01-31 19:07 ` Denis PILAT
2007-01-31 21:29 ` Nick Roberts
2007-02-01 9:49 ` Denis PILAT
2007-02-08 16:41 ` Daniel Jacobowitz
2007-02-08 19:33 ` Nick Roberts
2007-02-08 19:55 ` Daniel Jacobowitz
2007-02-09 15:43 ` Eli Zaretskii
2007-02-12 21:10 ` Denis PILAT
2007-02-13 0:11 ` Nick Roberts
2007-02-13 8:26 ` Denis PILAT
2007-02-20 16:06 ` Andreas Schwab
2007-02-20 16:17 ` Denis PILAT
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=17847.59449.255655.56503@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=denis.pilat@st.com \
--cc=frederic.riss@gmail.com \
--cc=gdb-patches@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