From: Jim Blandy <jimb@red-bean.com>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] add 'rs6000_in_function_epilogue_p()'
Date: Thu, 01 Dec 2005 05:21:00 -0000 [thread overview]
Message-ID: <8f2776cb0511302121k4b750269l4316b1e13a41debc@mail.gmail.com> (raw)
In-Reply-To: <200511301225.56802.pgilliam@us.ibm.com>
I'm not objecting to the patch, but following the links to the other
messages I didn't really see an explanation as to how incorrectly
recognizing the prologue causes the watchpoints to be deleted early.
I assume we're talking about a case like:
- we're in some function foo
- we set a watchpoint on one of its local variables
- we step through a call from foo to bar
- as we exit bar, the watchpoint gets deleted, even though it's in the
frame we're returning to, not the frame that is exiting.
Is that right? How does correctly recognizing the prologue fix this?
next prev parent reply other threads:[~2005-12-01 5:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:56 Paul Gilliam
2005-12-01 5:21 ` Jim Blandy [this message]
2005-12-01 18:27 ` Paul Gilliam
2005-12-01 20:14 ` Paul Gilliam
2005-12-02 1:13 ` Jim Blandy
2005-12-02 1:23 ` Daniel Jacobowitz
2005-12-02 20:12 ` Paul Gilliam
2005-12-02 20:17 ` Paul Gilliam
2005-12-03 3:05 ` Jim Blandy
2005-12-02 23:38 ` Jim Blandy
2005-12-04 20:19 ` Daniel Jacobowitz
2005-12-04 18:59 ` Daniel Jacobowitz
2005-12-04 20:48 ` Jim Blandy
2005-12-04 21:12 ` Jim Blandy
2005-12-04 21:16 ` Daniel Jacobowitz
2005-12-04 21:22 ` Jim Blandy
2005-12-02 4:02 ` Joel Brobecker
2005-12-02 18:44 ` Mark Kettenis
2005-12-02 19:15 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Paul Gilliam
2005-12-02 20:28 ` Mark Kettenis
2005-12-02 21:19 ` Daniel Jacobowitz
2005-12-02 21:21 ` Mark Kettenis
2005-12-03 4:53 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised, again) Paul Gilliam
2005-12-03 5:43 ` Paul Gilliam
2005-12-02 21:44 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Kevin Buettner
2005-12-06 15:20 ` Paul Gilliam
2005-12-06 15:15 ` Paul Gilliam
2005-12-08 4:42 ` Kevin Buettner
2006-01-11 17:44 ` Paul Gilliam
2006-01-12 0:12 ` Paul Gilliam
2006-01-12 23:53 ` Paul Gilliam
2006-01-13 21:05 ` Mark Kettenis
2006-01-17 3:46 ` Paul Gilliam
2006-01-17 19:29 ` Mark Kettenis
2006-02-09 17:46 ` Kevin Buettner
2005-12-02 22:19 ` Jim Blandy
2005-12-02 22:28 ` Daniel Jacobowitz
2005-12-02 23:20 ` Jim Blandy
2005-12-03 12:48 ` Paul Gilliam
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=8f2776cb0511302121k4b750269l4316b1e13a41debc@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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