On Thursday 27 March 2003 22:28, you wrote:
Yes, of course, and it can often breaks things, right? Most users of
cd/pwd seem to want to neglect the fact that the pwd state is
per-process not per-thread, so perhaps it would be simpler just to
give them that, thus side-stepping the locking
On Wednesday 26 March 2003 20:03, you wrote:
1. Are there ANY cases where a TLS (thread local storage) cd/pwd would
be the WRONG thing? E.g., could we reasonally expect there to be any
cases where one thread A does pwd, gets /home/my, does cd /foo,
and then thread B does pwd and EXPECTS to
On Thu, Mar 27, 2003 at 10:15:33AM +0100, Zoran Vasiljevic wrote:
On Wednesday 26 March 2003 20:03, you wrote:
1. Are there ANY cases where a TLS (thread local storage) cd/pwd would
be the WRONG thing? E.g., could we reasonally expect there to be any
cases where one thread A does pwd,
It seems that if people wanted to use generally-available TCL packages
inside AOL, it'd be nice if cd worked and was per-thread. Otherwise,
even if the TCL internals are fixed to lock around the temporary cd
fiddling it does in realpath or wherever else, ordinary TCL packages
still won't work in
Hi !
After some days... (yes, it is *always* very costly and difficult)
I've pinpointed a large hole in Tcl8.4.(1|2) which effectively
generates bogus OS paths, corrupts memory and otherwise impairs
the AOLserver (or any other MT-enabled application).
The problem is in Tcl generic/tclIOUtil.c
Yes, i am currently fighting with the same problem, under big load
when i do many calles to Tcl [file] command aolserver crashes
consistently in
static void FreeFsPathInternalRep(pathObjPtr),
but i do not do [cd], just [file mtime,stat,file]
When i do not do Tcl [file] command everything is
Zoran Vasiljevic wrote:
How come nobody has noticed this so far?
Well, the problem starts displaying itself if you ever change
the current directory of the process *after* the Tcl has been
initialized. You need not do [cd] explicitly; some internal
Tcl code does that on your behalf as well.
I
On Wednesday 26 March 2003 19:15, you wrote:
Yes, i am currently fighting with the same problem, under big load
when i do many calles to Tcl [file] command aolserver crashes
consistently in
static void FreeFsPathInternalRep(pathObjPtr),
but i do not do [cd], just [file mtime,stat,file]
When
On Wednesday 26 March 2003 19:12, you wrote:
Zoran Vasiljevic wrote:
How come nobody has noticed this so far?
Well, the problem starts displaying itself if you ever change
the current directory of the process *after* the Tcl has been
initialized. You need not do [cd] explicitly; some internal
On Wed, Mar 26, 2003 at 07:19:08PM +0100, Zoran Vasiljevic wrote:
Zoran Vasiljevic wrote:
Well, the problem starts displaying itself if you ever change
the current directory of the process *after* the Tcl has been
initialized. You need not do [cd] explicitly; some internal
Tcl code does
10 matches
Mail list logo
