Re: Task ids weird behavior

new topic     » goto parent     » topic index » view thread      » older message » newer message

Well, if you can't rely on a simple comparison to work as it usually does it can certainly create bugs in your programs. Seems like there is a type conversion missing somewhere.

I've also been having a problem recently with tasking where if I force a crash for debugging purposes (like with ? 1/0) just after a task_yield() statement, it will throw a machine-level error instead of a proper crash with .err files written with full debugging info. I can't as yet reproduce this behavior in a simple example, but it has happened quite a bit in programs that have complex task-switching.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu