Hi,
currently, when gdb interrupts a Xenomai application, all timers stop
firing (except for those marked with XNTIMER_NOBLCK - core timers). This
means, you can't debug one RT application without affecting others on
the same systems. I'm not wondering how to resolve this. Options:
- convert timer stopping to a per-process feature - implies the need to
establish some timer-process relationship concept, and it might be
tricky for drivers and other central timer creators
- let the application deal with timer overflows during debug:
- make timer stop optional (in case of single applications that
can't handle this yet)
- do not stop timers at all
Any opinions?
BTW, I also have pre/post-debug hook concept for applications out of
tree that can help to make applications debug-aware. In our use cases,
the pre-hook brings hardware into a state that permits application stop,
and the post-host ramps everything up again.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
_______________________________________________
Xenomai mailing list
[email protected]
https://xenomai.org/mailman/listinfo/xenomai
