Description of problem:
When using viper with serial download via GDB and asserts enabled, if you run
any test that allows interrupts to be enabled, e.g. bin_sem2, you get a spurious
I'll fix it (assuming I can convince bugzilla to assign this to myself), but it
won't be fixed in 2.0 beta 1.
What configuration makes this happen? I can't duplicate it, at least as of
CVS (root) on March 6.
v2.0 branch. With a RedBoot also built from the branch in case that makes a
difference. Enable asserts. Run bin_sem2. That's all!
I was only able to duplicate this with v2.0b program and RedBoot.
Using RedBoot built from the trunk does not suffer this assert, or at least
I couldn't make it happen.
This bug has moved to http://bugs.ecos.sourceware.org/show_bug.cgi?id=85755