[Tutor] Application Error after end of program

Danny Yoo dyoo@hkn.eecs.berkeley.edu
Mon, 10 Dec 2001 15:21:30 -0800 (PST)

On Mon, 10 Dec 2001, Lee-Shanok, Bruce wrote:

> >Once you make a (new) thread, it is as if you have two programs
> >running at the same time, but they share the same address space.  If
> >the "main" thread terminates (after that "last print" you mention) but
> >you have another non-daemon thread running, it keeps running.  The
> >program isn't over yet.
> I thought that might be it, but from the looks of it, I've pasted a
> print statement at the end of every run() method in my Thread object,
> which I understand is the very last command.. although I suppose the
> thread could switch over immediately after the pause, but I do a join
> for each thread from the main thread.

This might be something you want to post on the main comp.lang.python
newsgroup as well as Tutor.  These kind of errors should not happen in
Python, so perhaps someone on comp.lang.python might be able to point out
a service pack fix in NT that corrects this.

> >Heh, NTDLL.DLL?  Sounds to me like a (buggy!) system library.  On a
> >non-buggy system (or at least, less so) errors only happen in
> >applications, not in the system itself.  I don't know what's going on,
> >but I expect it is thread related.

Agreed; I don't think this has to do with your program, but with some
system library of the operating system.

Good luck to you.