When debugging a posix/threadx program (usbx demo) -- stepping into, say some_function, makes the gdb (sometimes) stop in _tx_linux_thread_suspend_handler function and stepping out and back in doesn't work.. If continued then GDB stops with error "ERROR: Unexpected GDB output from command "-exec-step ". Cannot find bounds of current function".
One option that works is to set breakpoint in some_function, but this kind of makes it tedious to manage growing list of breakpoints.. Is there a way to make GDB skip _tx_linux_thread_suspend_handler altogether and go directly to some_function?
Greetings!
When debugging a posix/threadx program (usbx demo) -- stepping into, say some_function, makes the gdb (sometimes) stop in _tx_linux_thread_suspend_handler function and stepping out and back in doesn't work.. If continued then GDB stops with error "ERROR: Unexpected GDB output from command "-exec-step ". Cannot find bounds of current function".
One option that works is to set breakpoint in some_function, but this kind of makes it tedious to manage growing list of breakpoints.. Is there a way to make GDB skip _tx_linux_thread_suspend_handler altogether and go directly to some_function?
Thanks in advance!