Fixed
Created: Sep 20, 2018
Updated: Dec 3, 2018
Resolved Date: Oct 15, 2018
Previous ID: LIN9-7514
Found In Version: 10.17.41.11
Fix Version: 10.17.41.12
Severity: Standard
Applicable for: Wind River Linux LTS 17
Component/s: Toolchain
When use gdb on host to remote debug multi-thread application, after attach to one of thread, after run application in gdb, will failed to pause it via Ctrl+c, it will show:
/*******************************************/
>(gdb)c
>^C^CThe target is not responding to interrupt requests.
>Stop debugging it? (y or n)
/*******************************************/
If debug normal application(not multi-thread), stop action can be done normally.
There is a similar issue in community(https://sourceware.org/bugzilla/show_bug.cgi?id=18945), after apply the patch in it, looks this issue can be fixed, if we can integrated this patch into our product.
I've setup the same env with customer with qemu img and customer's very complicated application.
I also reproduced with issue with qemu and the simple test code in attachment.
1.setup.sh && bitbake image
2.start qemu with the command 'make start-target EX_TARGET_QEMU_OPTS="-redir tcp:1234::1234" ' to bootup wrlinux
3.run gdbserver on target:
# gdbserver --multi :1234 &
and run application(compile the attached test sample), see the thread's pid
#./test &
4.on host, run gdb, and connect to target:
(gdb) target extended-remote :1234
5.then attach to child thread:
(gdb) attach xxx(child pid)
run it then try to pause it via Ctrl +c
(gdb) c
Continuing
Then ^C
