[vyskocil]

I play with e32.Ao.timer, e32.Ao_lock and e32.ao_callgate (bluetooth GPS handling is done in another thread) in a GPS program and I my program stop at a error :

E32USER-CBase 42

It happen when the program call lock.wait() twice in a row.

I think python shouldn't exit with this error (?)

[antonypr]

I haven't played with Python yet. However, according to Symbian C++ documentation, E32USER-CBase 42 panic happens when you try to activate an active object that is already active.

"This panic is raised by the SetActive() member function of an active object, a CActive. It is caused by an attempt to flag the active object as active when it is already active, i.e. a request is still outstanding."

May be you shouldn't call lock.wait() twice there.

[vyskocil]

As lock.wait() wait until a signal is raised it souldn't be wrong to call lock.wait() twice in the same thread for example :

while !self.exit:
lock.wait()

But lock.wait() let also user interface interraction and I think there is some race condition (?)

[simo.salminen]

Well at least the Ao_timer bugs, see this thread: http://discussion.forum.nokia.com/fo...ad.php?t=80922

Easiest thing to avoid your problem is to use the work-around mentioned on that thread.

ao_callgate bug and work-around: http://sourceforge.net/tracker/index...55&atid=790646