On 8/2/07, Neophytos Demetriou <[EMAIL PROTECTED]> wrote: > >> Zoran, just to make sure I got that right: xotcl does not work with the > >> nstrace/lazyloader at all (true or false). That's the reason I'm using > >> the modified init.tcl file from 4.99.1. > > > > I wonder if this is xotcl specific, or if xotcl just tickles the right > > (wrong) bit of code. Xotcl seems to use a lot of deeply namespaced > > commands, who's names are stored in variables... > > Stephen, there is no need for deeply namespaced commands (that's just > part of some code I wrote a couple of years back). > > > It would be really helpful if a minimal example of the error could be > > isolated in standard Tcl and dropped into a file: > > tests/testserver/modules/state.tcl > > > > Hard to write a test for it, but at least it will throw an error at > > startup when the tests are run and someone will see it. If it really > > is an xotcl-only error, I guess it can be package required in a catch > > or something? > > The problem with lazyloader=false should be easier to overcome (i.e. > serializing xotcl code + "ns_ictl trace allocate [list source > module-file]").
You'd be doing me a favor if you looked over these instructions for running tests I just put on the wiki and validated that they run a machine other than mine and are basically understandable: http://naviserver.sourceforge.net/wiki/index.php/Running_Tests Also, here's a start at testing the init sequence: http://naviserver.cvs.sourceforge.net/naviserver/naviserver/tests/init.test?view=markup If anyone can think of any expectations they have of the initialisation code that isn't already covered, just add them onto the end. Also also, it's worth mentioning that the nsd/init.tcl file can be substituted for another one using the config parameter ns/server/$server/tcl:initfile. We do that in the test suite config just to make sure the fresh source gets used: http://naviserver.cvs.sourceforge.net/naviserver/naviserver/tests/test.nscfg?view=markup#l_130 That should make it convenient to isolate differences between a complex installation and the basic upstream test environment. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
