thomas.frey at alumni.ethz.ch
Sat Sep 16 03:15:40 CEST 2006
As far as I know, the somewhat unhelpful stack trace was reverted to
the old trap handler in 3.4.06.
When developing multithreaded code you can consider the use of
DebugLog instead AosOut for more meaningful output. DebugLog uses a
different color for different threads, so the trace output can be
identified. It is also possible to have timestamps added to the trace
output. All output is identified by Module and Method of the "writer".
On 9/16/06, Søren Renner <soren.renner at gmail.com> wrote:
> For the first time I am trying to write multithreaded code in Active
> Oberon. The error messages in the kernel log are, so far, somewhat
> unhelpful. Should I revert to the previous alpha and its more helpful
> It will probably work itself out by the time anyone offers a
> suggestion. Cheers, your colleague sr.
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon