Stray signals in Symbian Active Objects
Article Metadata
With respect to the Active object framework in Symbian OS, Stray signal is a panic which is defined as E32USER-CBase 46.
There are following cases when stray signal may occur:
- CActiveScheduler::Add() was not called when the active object was constructed (it cause E32USER-CBase 49).
- SetActive() was not called following the submission of a request to the asynchronous service provider.
- The asynchronous service provider completed the TRequestStatus of an active object more than once – either because of "when an already-completed request is canceled" or "more than one request was submitted simultaneously on the same active object."
04 Sep
2009
This article provides very good cases to debug why a stray signal panic (E32USER-CBase 46) was thrown when using AO. For anyone working with AO, chances are more that he/she may encounter this panic. When encountered this article provides reasonable clue where to look for to fix it.
28 Sep
2009
Improper use of Active Objects may cause panic E32USER-CBase 46. Documentation says This panic is raised by an active scheduler, a CActiveScheduler. It is caused by a stray signal. But for beginners it is difficult to understand what is stray signals.
This article describes possible case which may generates stray signals. Although article is very small, it is very useful to understand how stray signals are generated.