From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <drow@false.org>
Subject: Re: [PATCH] Re: Unwinding CFI gcc practice of assumed `same value' regs
Date: Wed, 13 Dec 2006 22:11:00 -0000 [thread overview]
Message-ID: <20061213221111.GA26406@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <5950.82.92.89.47.1166046772.squirrel@webmail.xs4all.nl>
On Wed, 13 Dec 2006 22:52:52 +0100, Mark Kettenis wrote:
...
> No, sorry, it is me who is confused. I didn't actually look at Jan's patch
> and assumed it did the the right thing of marking the return address as
> undefined.
Therefore what should the patch do? Currently `.cfi_undefined' looks as too
radical.
GDB may check for `PC == 0 && strcmp (name, "clone") == 0' (more reliably).
That `strcmp (name, "clone")' needs to be coded in more trustworthy way.
This "outermost" framework is already present in GDB but it would mean to add
besides `set backtrace past-main' and `set backtrace past-entry' also some `set
backtrace past-clone' and several more others in the future.
Thanks,
Jan
next prev parent reply other threads:[~2006-12-13 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061211190300.GA4372@host0.dyn.jankratochvil.net>
[not found] ` <20061211224022.AD76E1800E7@magilla.sf.frob.com>
[not found] ` <20061212155233.GH29911@devserv.devel.redhat.com>
2006-12-13 20:46 ` Jan Kratochvil
2006-12-13 21:04 ` Daniel Jacobowitz
2006-12-13 21:41 ` Mark Kettenis
2006-12-13 21:46 ` Daniel Jacobowitz
2006-12-13 21:53 ` Mark Kettenis
2006-12-13 22:11 ` Jan Kratochvil [this message]
2006-12-16 23:46 ` Jan Kratochvil
2006-12-17 13:06 ` Mark Kettenis
2006-12-17 18:23 ` Jan Kratochvil
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=20061213221111.GA26406@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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