From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: functrace [was Re: funcstack and backtraces]
Date: Sun, 17 Sep 2006 19:38:45 -0400 [thread overview]
Message-ID: <20060917233845.GA32023@scowler.net> (raw)
In-Reply-To: <060917155254.ZM312@torch.brasslantern.com>
> Adding an extra level of function stack avoids the crash, but this
> still doesn't look right to me:
What crash?
> schaefer<505> (bar() { foo } ; foo() { print $functrace } ; bar )
> bar:0 Src/zsh:bar:0
>
> No mention of "foo" at all? Whose idea of useful is that? And here:
I was assuming that the function printing the trace would be able to
identify itself, but if not, "foo" is in $funcstack. Shouldn't be too
difficult to tack it on in functracegetfn if that's useful though.
> schaefer<506> (baz() { bar };
> bar() { foo } ;
> foo() { print $functrace } ;
> baz )
> bar:0 baz:0 Src/zsh:bar:0
> What does that it mean that "bar" is at both ends of the stack?
I can't reproduce that. I get
bar:0 baz:0 Src/zsh:6
(or Src/zsh:0 Src/zsh:0 Src/Zsh:12)
> You're right about it being buggy when functionargzero is not set.
> Even the examples above that don't crash when it is set, crash when
> it is not set (with effectively the same backtrace).
I can't reproduce that either.
next prev parent reply other threads:[~2006-09-17 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 19:10 funcstack and backtraces Clint Adams
2006-09-04 21:26 ` Bart Schaefer
2006-09-04 23:15 ` Clint Adams
2006-09-17 19:14 ` PATCH: functrace [was Re: funcstack and backtraces] Clint Adams
2006-09-17 22:39 ` Bart Schaefer
2006-09-18 3:37 ` Clint Adams
2006-09-18 5:57 ` Bart Schaefer
2006-09-18 11:07 ` Clint Adams
2006-09-18 15:16 ` Bart Schaefer
2006-09-17 22:52 ` Bart Schaefer
2006-09-17 23:38 ` Clint Adams [this message]
2006-09-18 2:20 ` Bart Schaefer
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=20060917233845.GA32023@scowler.net \
--to=clint@zsh.org \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).