From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: advice on reducing C stack frame size?
Date: Tue, 16 Sep 2008 19:57:29 +0200 [thread overview]
Message-ID: <m31vzk6kja.fsf@pobox.com> (raw)
In-Reply-To: <7683D3EC-06F5-407D-B353-E5E7BB1836EA@raeburn.org> (Ken Raeburn's message of "Tue, 16 Sep 2008 01:27:45 -0400")
Hi,
On Tue 16 Sep 2008 07:27, Ken Raeburn <raeburn@raeburn.org> writes:
> On Sep 13, 2008, at 12:56, Andy Wingo wrote:
>> So for example, just sitting at the repl, we have:
>>
>> #28 0x001c48fc in vm_run (vm=0xb7f1ff58, program=0x8d53df8,
>> #29 0x001bfcad in program_apply (program=0xb7ee2730, args=0x404) at
>>
>> The difference between #29 and #28 is the size of the vm_run() stack
>> frame (I think).
>
> Aren't those the program counter addresses you're looking at?
Probably so, stupid me. Showing my ignorance in public.
They give us git-rebase so our patches can be perfect once pushed -- but
nothing for mailing lists! ;)
> Try "print $sp" or "info reg" at each frame to see the stack pointer.
Thanks!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2008-09-16 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 16:56 advice on reducing C stack frame size? Andy Wingo
2008-09-13 18:48 ` Han-Wen Nienhuys
2008-09-14 16:46 ` Neil Jerram
2008-09-16 5:27 ` Ken Raeburn
2008-09-16 17:57 ` Andy Wingo [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31vzk6kja.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).