From: "Rocky Bernstein" <rocky.bernstein@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Weird exit caused in a trap DEBUG which sources a file.
Date: Wed, 30 Jul 2008 22:38:23 -0400 [thread overview]
Message-ID: <6cd6de210807301938m28e05c84vf6296aa5b1bc0d44@mail.gmail.com> (raw)
Below is a small program whittled down from a larger one. It has
behavior I can't figure out.
It seems to show that when a function is called via trap DEBUG and you
then source a file and it has a statement in it, on return from the
TRAP an exit will be taken. Here is the program:
#!/usr/bin/zsh
function debug_trap_handler {
print $functrace[1]
do_bug
}
function do_bug {
. ./bug-file
}
trap 'echo EXIT hit' EXIT
trap 'debug_trap_handler' DEBUG
a=1
b=2
d=3
In "bug-file" put any command. ":" will do. Or a print statement.
Let's say it contains the line:
print bug file here
When I run the above I get:
$ ./zshtrace.sh
./zshtrace.sh:12
bug file here
EXIT hit
Now if the file contains only comments or blank lines or is empty,
here is what I get:
$ ./zshtrace.sh
./zshtrace.sh:12
./zshtrace.sh:13
./zshtrace.sh:14
./zshtrace.sh:15
EXIT hit
which is what I would expect.
Anyone care to venture a guess as to what's going on? It feels like a
bug to me, if for no other reason than some message about why the exit
was raised is missing.
Thanks.
next reply other threads:[~2008-07-31 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 2:38 Rocky Bernstein [this message]
2008-07-31 9:01 ` Peter Stephenson
2008-07-31 10:05 ` Rocky Bernstein
2008-08-01 12:29 ` Rocky Bernstein
2008-08-01 13:37 ` Peter Stephenson
2008-08-01 15:21 ` Rocky Bernstein
2008-08-01 15:31 ` Peter Stephenson
2008-08-02 11:21 ` Rocky Bernstein
2008-08-03 10:42 ` Peter Stephenson
2008-08-03 11:28 ` Rocky Bernstein
2008-08-03 11:50 ` Peter Stephenson
2008-08-05 11:18 ` Rocky Bernstein
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=6cd6de210807301938m28e05c84vf6296aa5b1bc0d44@mail.gmail.com \
--to=rocky.bernstein@gmail.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).