Thanks for looking at that Gustaf.
I can definitely relate to Zoran's comment:
> "In the moment all is pretty "spooky" and it is difficult to grasp..."
Your change doesn't seem to help the problems I'm looking at here
unfortunately.
The output you have pasted is the same as mine up to that point. I wouldn't
have seen an error by then either.
It's the *subsequent* calls to "clock scan" and "::try {} on error .."
which then fail.
To illustrate I made a bash script (which needs run by sudo) which starts
up naviserver to a prompt:
#!/bin/bash
hg clone https://bitbucket.org/naviserver/naviserver
cd naviserver
./autogen.sh --disable-ipv6 --with-tcl=/usr/lib/tcl8.5 --enable-rpath
--enable-threads --enable-symbols
make
make install
cat <<EOF >/usr/local/ns/tcl/test.tcl
package require try
::try {
ns_log Notice "[clock scan "+365 days"]"
} on error [list message options] {
ns_log Notice "$message"
ns_log Notice "$options"
}
EOF
chown nsd:nsd -R /usr/local/ns/logs
/usr/local/ns/bin/nsd -u nsd -t /usr/local/ns/conf/nsd-config.tcl -c
After this bash script is run, on Debian Stretch, the following commands
will fail in the Naviserver interpreter:
% ::try { puts trying } on error [list message options] { puts error }
can't read "magicCodes": no such variable
% clock scan "+365 days"
invalid command name "::tcl::clock::scan"
It's quite a contrived testcase - the same errors are occurring more
naturally within our "full" environment.
--
David
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
