From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: __builtin_frame_address vs %esp in pt-machine.h
Date: Fri, 18 Oct 2002 13:04:00 -0000 [thread overview]
Message-ID: <200210182002.g9IK2Jk18646@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Saturday, 5 October 2002 15:06:09 -0700 <3D9F6251.30000@redhat.com>
> The problem is the ptlongjmp.c code. For its use of CURRENT_STACK_FRAME
> the value must be as accurate as possible since otherwise the detection
> of frames which have to be handled might be wrong.
I don't understand this. Its use is to check whether another frame's auto
variable address might be below (off the top) of the current stack.
Another frame's variable could never be between the cleanup function's %ebp
and %esp--that's its own frame. So using %esp is fine there.
next prev parent reply other threads:[~2002-10-18 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 15:06 Roland McGrath
2002-10-06 13:24 ` Ulrich Drepper
2002-10-18 13:04 ` Roland McGrath [this message]
2002-10-18 20:43 ` Ulrich Drepper
2002-11-06 0:58 ` Roland McGrath
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=200210182002.g9IK2Jk18646@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).