From: Stan Shebs <shebs@apple.com>
To: Christopher Faylor <me@cgf.cx>
Cc: roland.schwingel@onevision.de, gdb@sourceware.org
Subject: Re: gdb stack trace problems (Addendum)
Date: Mon, 09 May 2005 05:30:00 -0000 [thread overview]
Message-ID: <427EF55B.8090503@apple.com> (raw)
In-Reply-To: <20050508231953.GG3896@trixie.casa.cgf.cx>
Christopher Faylor wrote:
>
>If a function doesn't set up a frame pointer and there is no debugging
>information available, how would one derive a stack frame? I could
>imagine a really complicated "search the stack" technique but I can't
>see how it would ever be foolproof.
>
That's where GDB hacking just starts to get interesting. :-) Yes,
it's complicated and potentially expensive too, because you may have
to transfer a lot of bytes. The mips has something similar for
function starts, and a "heuristic-fence-post" variable to control
how hard to work at it.
Stan
next prev parent reply other threads:[~2005-05-09 5:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 7:04 Roland Schwingel
2005-05-08 13:31 ` Mark Kettenis
2005-05-08 23:20 ` Christopher Faylor
2005-05-09 4:48 ` Eli Zaretskii
2005-05-09 5:26 ` Christopher Faylor
2005-05-09 5:30 ` Stan Shebs [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 8:39 Roland Schwingel
2005-05-10 8:38 Roland Schwingel
2005-04-26 11:53 Roland Schwingel
2005-04-26 9:11 Roland Schwingel
2005-04-25 12:35 Roland Schwingel
2005-04-25 8:00 ` Roland Schwingel
2005-04-25 19:35 ` Mark Kettenis
2005-04-25 19:45 ` Daniel Jacobowitz
2005-04-25 20:37 ` Mark Kettenis
2005-04-19 8:01 Roland Schwingel
[not found] ` <4268B942.5080300@onevision.de>
2005-04-22 17:51 ` Mark Kettenis
2005-04-19 7:34 Roland Schwingel
2005-04-19 7:45 ` Mark Kettenis
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=427EF55B.8090503@apple.com \
--to=shebs@apple.com \
--cc=gdb@sourceware.org \
--cc=me@cgf.cx \
--cc=roland.schwingel@onevision.de \
/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