From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] The off again, on again, PC == 0 in get_prev_frame
Date: Sun, 22 Feb 2004 21:10:00 -0000 [thread overview]
Message-ID: <200402222110.i1MLAAlH000732@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <4038E9A5.2090601@gnu.org> (message from Andrew Cagney on Sun, 22 Feb 2004 12:40:53 -0500)
Date: Sun, 22 Feb 2004 12:40:53 -0500
From: Andrew Cagney <cagney@gnu.org>
> The Linux folks should add proper CFI to the implementation of
> close(2) in glibc. A DW_CFA_def_cfa rule that sets the CFA to %rbp
> should do the trick.
clone(2)?
Yup. Sorry. Typo. The thread_start you're seeing in the backtrace
is part of the clone(2) implementation in glibc.
See sysdeps/unix/sysv/linux/x86_64/clone.S.
How come the trad unwind code doesn't recover?
There simply isn't a frame pointer.
Thinking about it, the test would stop this backtrace:
sigsegv_handler
<signal trampoline>
"null"
foo (which called "null")
main
is this tested anywhere?
No it isn't.
Mark
prev parent reply other threads:[~2004-02-22 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 21:27 Andrew Cagney
2004-02-20 23:23 ` Mark Kettenis
2004-02-22 17:40 ` Andrew Cagney
2004-02-22 21:10 ` Mark Kettenis [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=200402222110.i1MLAAlH000732@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@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