A natural consenquence of what I found yesterday was
that I had to try to delete the 'class' definition from the
namespace. Adding this line

::itcl::delete class $fun(function_class)

seems to prevent the process from crashing and
therefore might be a workaround. I'm testing
the code right now refreshing the page every 20 seconds,
and I haven't got any crash in 30
minutes, whereas prior to that crashes were
quite easy to get. It doesn't provide for an explanation but
at least one knows where the thin ice is and can avoid
to walk over it.

David Welton wrote:

Here is what I found (I hope I don't get too specific)
The line that screws everything up is in a method where various
parts of a page are dynamically generated. The 'modules'
that generate these sections of the page are implemented through
classes which in turn are sourced by a method invoked by the
main template.

I verified that the 'sourcing' of these classes' files
breaks the rivet process (although the code 'per se'
is functioning!).


So if you don't source them, no crash?


no crash. Sourcing is enough for getting a crash, I don't
need to instantiate or execute methods.



Hrm...  is it possible to replicate the crash in a 'clean' environment
that is as simple as possible?

no, I tried but I failed. I created a class that sources in another class
definition, makes an object, runs some code and the cleans the object
up (not the class). It seems that same case, but it doesn't crash.
I can provide the code, its about 40 lines, empty lines included



It should be possible to build the '1.0' branch on debian stable, I think.

I will try then. David, is there any facility for writing lines in
the apache error log? Just to facilitate the synchronization between
the session and the apache log files.

--
-- Massimo Manghi
-- Dipartimento di Biologia Evolutiva e Funzionale
-- Università degli Studi di Parma
-- Parco Area delle Scienze 11A - 43100 Parma


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to