From: Andrew Cagney <cagney@gnu.org>
To: Roland McGrath <roland@redhat.com>, Mark Kettenis <kettenis@jive.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Identifying bottom-of-stack
Date: Wed, 11 Aug 2004 17:51:00 -0000 [thread overview]
Message-ID: <411A5C6E.5000904@gnu.org> (raw)
In-Reply-To: <200408052018.i75KIXAZ023214@magilla.sf.frob.com>
> [Andrew says:]
>
>>>> > > - GLIBC marking those outermost frames with CFI indicating that both the
>>>> > > CFA and the RA are "unknown"?
>>
>>>
>>> s/unknown/undefined/
>
>
> Perhaps this addresses Mark's request for precision in terminology, but it
> doesn't clarify anything for me. Does this "undefined" mean the
> "undefined" used in the DWARF spec? Does DW_CFA_def_cfa with some register +
> DW_CFA_undefined on that register in fact yield this? Is that the only way
> to produce it?
Yes. CFA's "undefined", that would yield what we need.
> Is it the optimal way?
I don't know.
> These are the questions I meant to imply when I asked,
> "What would such CFI look like exactly?"
>
> If you want me to do it, step one is always to specify it completely.
I gather that no one's found a hole in the theory, I guess it is time to
prototype it in, I guess, GDB's testsuite.
Andrew
prev parent reply other threads:[~2004-08-11 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 16:01 Andrew Cagney
2004-08-04 17:17 ` Daniel Jacobowitz
2004-08-04 18:12 ` Andrew Cagney
2004-08-04 18:03 ` Daniel Jacobowitz
2004-08-04 18:31 ` Andrew Cagney
2004-08-04 19:02 ` Roland McGrath
2004-08-05 9:42 ` Mark Kettenis
2004-08-05 13:03 ` Andrew Cagney
2004-08-05 20:18 ` Roland McGrath
2004-08-11 17:51 ` Andrew Cagney [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=411A5C6E.5000904@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@jive.nl \
--cc=roland@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