Philippe Gerum wrote: >> However, terminating gdb and restarting app outside gdb >> does make RTDM task resume execution. Before, the driver had to be reloaded. >> >> So gdb appears to be causing timer to block even if no breakpoint is set, >> probably signals? >> > > There is no reason for that. Sending "continue" to gdb is expected to > unblock the timers, until the code is single-stepped again (e.g. after > ^C or any breakpoint).
gdb silently intercepts a traced program for various reasons, e.g. thread creation or library loading. Even if no user breakpoint is set, the program may briefly be stopped nevertheless. If that happens frequently enough, and every stop can add latencies to running timers... Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
