From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: functrace [was Re: funcstack and backtraces]
Date: Sun, 17 Sep 2006 22:57:33 -0700 [thread overview]
Message-ID: <060917225733.ZM1116@torch.brasslantern.com> (raw)
In-Reply-To: <20060918033708.GA6522@scowler.net>
On Sep 17, 11:37pm, Clint Adams wrote:
}
} Operator precedence might be a good thing to pay attention to,
} though I don't know if it's your problem.
That does in fact seem to have stopped the crash.
There just seems to be one more problem: It looks as if functrace and
funcstack are indexed in the opposite order from one another? Would it
not be better if they were in parallel? Or am I misreading this?
schaefer<506> TRAPDEBUG() { print $funcstack ; print $functrace }
TRAPDEBUG
Src/zsh:8
TRAPDEBUG precmd
Src/zsh:1 Src/zsh:9
TRAPDEBUG title precmd
title:1 Src/zsh:1 Src/zsh:9
TRAPDEBUG title precmd
title:2 Src/zsh:1 Src/zsh:9
TRAPDEBUG precmd
Src/zsh:1 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:1 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:2 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:6 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:7 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:8 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:11 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:12 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:1 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:15 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:12 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:19 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:20 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:23 Src/zsh:2 Src/zsh:9
TRAPDEBUG prompt_bart_precmd precmd
prompt_bart_precmd:26 Src/zsh:2 Src/zsh:9
TRAPDEBUG precmd
Src/zsh:2 Src/zsh:9
torch [TRAPDEBUG() { print $funcstack ; print $functrace }] /usr/src/local/zsh
schaefer<507>
next prev parent reply other threads:[~2006-09-18 5:57 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 [this message]
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
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=060917225733.ZM1116@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).