From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rodney.bates@wichita.edu, gdb@sourceware.org
Subject: Re: breakpoint for accessing memory location
Date: Sun, 22 Oct 2006 04:22:00 -0000 [thread overview]
Message-ID: <20061022042230.GA28995@nevyn.them.org> (raw)
In-Reply-To: <u8xj9oufd.fsf@gnu.org>
On Sun, Oct 22, 2006 at 06:17:58AM +0200, Eli Zaretskii wrote:
> > Date: Sat, 21 Oct 2006 18:32:00 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: rodney.bates@wichita.edu, gdb@sourceware.org
> > >
> > > So you are saying that "watch p - p" will also cause an error message
> > > when p goes out of scope?
> >
> > Well, I just tried it; that's what I'd expect, and it seems to be what
> > happens, also.
>
> That's silly, IMHO. Don't you think we should be smarter? Perhaps
> some kind of expression optimizer could be devised to do better.
I really don't think we should be optimizing expressions. One
certainly could be devised - but it would look like "fold" in GCC,
which is a huge and horrendously complex thing.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-22 4:22 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 20:10 Erik Leunissen
2006-10-19 20:12 ` Daniel Jacobowitz
2006-10-19 20:24 ` Erik Leunissen
2006-10-19 20:25 ` Daniel Jacobowitz
2006-10-19 20:28 ` Erik Leunissen
2006-10-20 6:31 ` Eli Zaretskii
2006-10-20 14:27 ` Daniel Jacobowitz
2006-10-21 13:20 ` [commit] Fix annotations-related index entries (was: breakpoint for accessing memory location) Eli Zaretskii
2006-10-20 16:56 ` breakpoint for accessing memory location Erik Leunissen
2006-10-20 17:39 ` Eli Zaretskii
2006-10-21 12:58 ` Eli Zaretskii
2006-10-21 22:28 ` Erik Leunissen
2006-10-22 4:20 ` Eli Zaretskii
2006-10-22 9:11 ` Erik Leunissen
2006-10-22 9:19 ` Erik Leunissen
2006-10-22 22:16 ` Eli Zaretskii
2006-10-23 7:41 ` Erik Leunissen
2006-10-21 15:06 ` Rodney M. Bates
2006-10-21 15:27 ` Daniel Jacobowitz
2006-10-21 15:29 ` Eli Zaretskii
2006-10-21 15:51 ` Daniel Jacobowitz
2006-10-21 21:26 ` Eli Zaretskii
2006-10-21 22:32 ` Daniel Jacobowitz
2006-10-22 4:18 ` Eli Zaretskii
2006-10-22 4:22 ` Daniel Jacobowitz [this message]
2006-10-22 12:18 ` Robert Dewar
2006-10-22 22:18 ` Eli Zaretskii
2006-10-22 22:21 ` Daniel Jacobowitz
2006-10-22 22:29 ` Eli Zaretskii
2006-10-22 22:49 ` Robert Dewar
2006-10-22 23:18 ` Daniel Jacobowitz
2006-10-23 2:03 ` Robert Dewar
2006-10-23 4:11 ` Eli Zaretskii
2006-10-23 12:36 ` Daniel Jacobowitz
2006-10-22 22:48 ` Robert Dewar
2006-10-22 22:51 ` Eli Zaretskii
2006-10-22 22:55 ` Robert Dewar
2006-10-23 4:10 ` Eli Zaretskii
2006-10-22 20:40 ` Mark Kettenis
2006-10-21 18:07 ` Rodney M. Bates
2006-10-21 21:42 ` Eli Zaretskii
2006-10-21 18:55 ` Rodney M. Bates
2006-10-21 21:53 ` Eli Zaretskii
2006-10-22 15:20 ` Rodney M. Bates
2006-10-22 17:24 ` Daniel Jacobowitz
2006-10-22 22:22 ` Eli Zaretskii
2006-10-23 22:02 ` Jim Blandy
2006-10-24 4:32 ` Eli Zaretskii
2006-10-24 12:57 ` Daniel Jacobowitz
2006-10-24 17:37 ` Eli Zaretskii
2006-10-24 17:41 ` Daniel Jacobowitz
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=20061022042230.GA28995@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=rodney.bates@wichita.edu \
/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