This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: "The target is not responding to interrupt requests" after re-attach
- From: Pedro Alves <palves at redhat dot com>
- To: Dmitry Antipov <dantipov at nvidia dot com>, GDB Development <gdb at sourceware dot org>
- Date: Thu, 19 Oct 2017 12:39:03 +0100
- Subject: Re: "The target is not responding to interrupt requests" after re-attach
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B5C0D13206
- References: <6c9c532c-8094-9df5-1a8c-556ea92a9b5a@nvidia.com>
On 10/17/2017 03:02 PM, Dmitry Antipov wrote:
> But it doesn't work for the next time:
>
> $ gdb -q
> (gdb) set sysroot /
> (gdb) target extended-remote :8888
> Remote debugging using :8888
> (gdb) attach 9320
> Attaching to process 9320
> Reading symbols from /tmp/t-nanosleep...done.
> Reading symbols from /lib64/libc.so.6...(no debugging symbols
> found)...done.
> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
> found)...done.
> 0x00007eff44c65420 in __nanosleep_nocancel () from /lib64/libc.so.6
> (gdb) c
> Continuing.
> ^C
> ^CThe target is not responding to interrupt requests.
> Stop debugging it? (y or n) y
>
> Even if it works as expected, what are the reasons for being
> inconsistent here?
>
No good reason. Sounds like you found a bug.
Thanks,
Pedro Alves