thread & y-tasks crash monitor

[ecostanza]

Hello.

This code:

import thread
import e32

class Downloader(object):
    def __init__(self):
        self._completed = False
        
    def start(self):
        thread.start_new_thread(self.run, ())
        
    def run(self):
        # waste some time..
        for i in range(1000):j = i*i/10.0
        self._completed = True

    def completed(self):
        return self._completed

d = Downloader()
d.start()
counter=0
while d.completed() == False:
    print unicode(counter)
    counter+=1
    e32.ao_sleep(0.01)
print u'done'

produces the expected output, but if I turn on the "crash monitor" in DrJukka.com's y-tasks v 0.51 I get the following error message:
"Py_{number}
Terminate: 0", where {number} changes every time and seems to indicate the thread ID.
(in the y-tasks detailed info it tells me "exit category: terminate, exit type: terminate")
I tried this on an E51.

Is this normal, or am I doing something wrong?
Why is the thread termination handled in a way that is recognized by y-tasks as a crash? Is it an issue with my code, with y-tasks, or with pys60?

Thanks,
Enrico

[GameDude]

Terminate: 0

0 == KErrNone, which means it terminated ok.

There is a line in thread_symbian.h:

RThread().Terminate(0);

Which I believe is the reason why Y-tasks catches it. And this is a normal behavior. Nothing wrong happening. It seems that if there are problems, Python panics.

[ecostanza]

Thanks for your reply!

There is a line in thread_symbian.h:

RThread().Terminate(0);

I read in the RThread::Terminate() documentation:

This function behaves in the same way as Kill()
...
A thread can also end itself by calling User::Exit()

I wonder if it would be possible to close the thread by using User::Exit() instead, and if that would be better -- from my point of view it is convenient to use a tool like ytasks to try and find out if there is anything going wrong in my app, but it's difficult to do it if I am inundated by "terminate" messages, so it is in this spirit that if these messages were removed it would be "better".

It seems to me that RThread::Terminate() is called from the thread which is actually exiting (i.e. not from another thread).

Thoughts?

Best,
Enrico

[GameDude]

Well, I'm not sure why the Terminate is even called. If you check the RThread example code from Wiki, Terminate is not called. I believe thread would exit cleanly if Terminate was not called at all.

I tested removing Terminate() on emulator and it didn't seem to cause any trouble.