From: Jim Blandy <jimb@red-bean.com>
To: Christophe LYON <christophe.lyon@st.com>
Cc: gdb@sourceware.org
Subject: Re: watchpoint and function epilogue
Date: Mon, 21 Nov 2005 17:31:00 -0000 [thread overview]
Message-ID: <8f2776cb0511210931t21ba726cmf6059a6f3f79f8d4@mail.gmail.com> (raw)
In-Reply-To: <4381CCD0.2060905@st.com>
[Accidentally dropped CC]
On 11/21/05, Christophe LYON <christophe.lyon@st.com> wrote:
> Jim Blandy wrote:
> > On 11/18/05, Christophe LYON <christophe.lyon@st.com> wrote:
> >
> >>So what is your advice in order to deal with this situation? I guess
> >>that if the compiler is modified not to generate the instruction that
> >>restores the CFA_offset, it will work again. Is there any other possibility?
> >
> >
> > You could emit a location list that says that 'b' is optimized out
> > starting at L3. I'm not sure how GDB would react to that, but it
> > would certainly be GDB's problem if it didn't behave correctly.
> >
>
> Thanks,
>
> I am not sure I can easily do that.
>
> No other target has the same kind of issue?
Actually, lots of targets have this issue. That test in the test suite
often has failures related to the compiler not quite accurately
describing when the variable is deallocated.
Another possibility would be to locate 'b' and all your other local
variables in a made-up internal lexical block which ends at L2.
prev parent reply other threads:[~2005-11-21 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 17:05 Christophe LYON
[not found] ` <8f2776cb0511181247l274c8c38y3a355d8f3eed92f8@mail.gmail.com>
[not found] ` <4381CCD0.2060905@st.com>
2005-11-21 17:31 ` Jim Blandy [this message]
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=8f2776cb0511210931t21ba726cmf6059a6f3f79f8d4@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=christophe.lyon@st.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).