From: Xin Zhao <uszhaoxin@gmail.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is stack back trace possible if compiled with -fomit-frame-pointer?
Date: Wed, 21 Sep 2005 10:50:48 -0400 [thread overview]
Message-ID: <4ae3c14050921075031fced13@mail.gmail.com> (raw)
In-Reply-To: <4331746F.9010500@stesmi.com>
Thanks for your reply.
But I am looking for a tool or method to do stack backtrace
automatically, not debug manually.
The tool listed on http://www.aivosto.com/visustin.html can only
generate control flow from source code. But I need a control flow
generator that can generate control flow from binary codes. One
example is EEL (Executable Edit Library). But it only works for SPARC
machine, not PC. :(
As for the question about the kernel development list, I am developing
a kernel module that supports stack backtrace and can analyze user app
binaries to enforce security policies. So this is still related to
Kernel development. :)
Xin
On 9/21/05, Stefan Smietanowski <stesmi@stesmi.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Xin Zhao wrote:
> > Also, I might want to know whether it is common case that linux apps
> > are compiled with -fomit-frame-pointer swtich?
>
> This is the Linux KERNEL development list.
>
> Not Linux USERSPACE development list.
>
> Find an appropriate list and ask your question there please.
>
> // Stefan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
>
> iD8DBQFDMXRvBrn2kJu9P78RAtlSAJwOMuF3mA9oxQO6nLwsHTCmf9lngACgkfOQ
> XMpu/ZFfdokiJ7jFSRCpvvQ=
> =Q3QR
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2005-09-21 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 14:37 Is stack back trace possible if compiled with -fomit-frame-pointer? Xin Zhao
2005-09-21 14:55 ` Stefan Smietanowski
2005-09-21 14:50 ` Xin Zhao [this message]
2005-09-21 15:25 ` Alistair John Strachan
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=4ae3c14050921075031fced13@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stesmi@stesmi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.