Very Computer

I am try to debug some code whos execution is initiated by an interrupt.
However, when running the de* the interrupt doesn't fire.

Is this by design? I seem to remember being able to do this under PB3. What
is the best way to debug this code?

--
Howard Swope
Software Engineer
Spitz, Inc [http://www.veryComputer.com/]

the Kernel De* in PB is the best way to do that and it works in V4.x as
it did in V3.0

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com

For some reason my interrupt is not firing in my debug build. I can set
break points in my driver code and they hit, but any of the code that is
triggered by an interrupt doesn't seem to get called. It works fine in the
release build.

Any ideas???

Quote:> the Kernel De* in PB is the best way to do that and it works in V4.x
as
> it did in V3.0

> --
> Steve Maillet (eMVP)
> Entelechy Consulting
> smaillet_AT_EntelechyConsulting_DOT_com

Sounds like a #ifdef DEBUG problem that is effecting the ISR so that the
event is never triggered for the IST. I'd look at how you set up the ISRs
and then examine the ISR itself and ALL #defines those use to make sure
something isn't bracketed in a #ifndef DEBUG that shouldn't be.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com