This is the mail archive of the
mailing list for the GDB project.
Re: debug of multithreaded program turns to be impossible during execution
- From: Pedro Alves <palves at redhat dot com>
- To: Avi Gozlan <avi at checkpoint dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 19 Aug 2014 17:05:51 +0100
- Subject: Re: debug of multithreaded program turns to be impossible during execution
- Authentication-results: sourceware.org; auth=none
- References: <71C49BB0B847984EAADFE43F93C6BF083ADA7BE0 at DAG-EX10 dot ad dot checkpoint dot com> <53DA17B5 dot 10703 at redhat dot com> <71C49BB0B847984EAADFE43F93C6BF083ADA8F07 at DAG-EX10 dot ad dot checkpoint dot com>
On 08/14/2014 04:52 PM, Avi Gozlan wrote:
> GDB 7.8 yields a similar behavior:
> (gdb) c
> [New Thread 0x43c05940 (LWP 3311)]
> [New Thread 0x44606940 (LWP 3312)]
> [Thread 0x44606940 (LWP 3312) exited]
> [Switching to Thread 0x43c05940 (LWP 3311)]
> Cannot remove breakpoints because program is no longer writable.
> Further execution is probably impossible.
> 0x00002aaaab98348f in start_thread () from /lib64/libpthread.so.0
> ptrace: No such process.
> (gdb) [Thread 0x46409940 (LWP 3315) exited]
> [Thread 0x45a08940 (LWP 3314) exited]
> [Thread 0x43c05940 (LWP 3311) exited]
> [Inferior 1 (process 3268) exited normally]
> The only difference is that in 7.8 case, GDB continues automatically after giving the ptrace message.
Any chance you could try your reproducer with a more recent
system? Mainly, I'm wondering whether kernel/glibc are at play here.
Also, a run with:
set debug infrun 1
set debug target 1
set debug lin-lwp 1
may help diagnose the issue.