Re: Tcl crashes

From: Steve Bold (stevebold_at_hotmail.com)
Date: 06/28/04 

Date: Mon, 28 Jun 2004 21:38:01 +0100

If you can get Tcl, Tk, Itcl and whatever extensions you used compiled
for debug, you can run the application under a C debugger and see where
its crashing. This might resolve the cause of the problem.

However, an intermittent crash is often indicative of memory management
problems and those are harder to debug. Tcl has some memory debugging
capabilities that might help. You may also want to consider dedicated
memory debugging tools. The one I use is Purify on Solaris, I belive it is also available
for HP/UX. It is expensive and slows down execution of the app substantially.
However, it is effective in reporting misuse of memory and in showing
enough context to make sense of the failure.

"Joseph Kaufman" <jkaufman@siac.com> wrote in message news:be9d3402.0406281140.27bd85a@posting.google.com...
> First, this application is written under the HP-UX operating system.
> GUI A comes up first in the morning. Then the outside event that
> triggers the launching of GUI B does not occur until an hour later. On
> most days there is no crash. When a crash occurs, the time of the
> crash varies, it can be morning, or afternoon, or late afternoon. I
> also want to add, the application is launched in the morning, and from
> then on nobody is touching it.
> "Georgios Petasis" <petasis@iit.demokritos.gr> wrote in message news:<cbpbss$1vr1$1@ulysses.noc.ntua.gr>...
> > I have also an incr tcl program, which always crashes
> > if an error is generated while the app is loading.
> > I.e., if a tcl error happens before tk enters the idle
> > state, the app always crashes under windows.
> > Of course other errors since this point are reported as
> > expected. And crashes never happen under linux.
> >
> > Perhaps this is also your case? Is an error occuring
> > while your app is loading? Or it crashes after the GUI has been
> > shown?
> >
> > George
> >
> > "Joseph Kaufman" <jkaufman@siac.com> wrote in message
> > news:be9d3402.0406280559.7065d7ac@posting.google.com...
> > > I have an [incr]Tcl GUI application, S. Typing S at the prompt brings
> > > up GUI A at the terminal IP. Later on, at some point due to a certain
> > > outside event, S launches GUI B, as a toplevel widget, to a remote IP.
> > > This means, S manages 2 GUIs, GUI A at the terminal IP, and GUI B at a
> > > remote IP. It happens at times, not always, that GUI A crashes, and
> > > with it the entire application S crashes. My suspicion is, the remote
> > > IP where GUI B is goes out of existence, brings down GUI B, and this
> > > in turn brings down GUI A. I have no way of checking GUI B since it is
> > > at a remote site.
> > >
> > > This same application, a) when there is no GUI B, or b) GUI B is
> > > launched at the terminal IP where GUI A is, has never crashed.
> > >
> > > My first design was, GUI B was a separate TCL script and S
> > > communicated with it through a socket. Then, also GUI A never crashed.
> > > The problem started when I made GUI B a part of S as an [incr]Tcl
> > > class. This bolsters my suspicion that GUI B is the culprit.
> > >
> > > Your help is greatly appreciated. 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.710 / Virus Database: 466 - Release Date: 24/06/2004