[RFC] 10/10 non-stop for linux native

[Pedro Alves]

A Tuesday 06 May 2008 16:50:10, Pedro Alves wrote:
> This adds non-stop support for linux native.
>
> The changes are:
>
> - ptracing a running thread doesn't work.
>
>  This implies that, we must ensure that the proc_services
>  usage in linux-thread-db.c talks to a pid of a stopped lwp.
>
>  Checking if a thread is alive with ptrace doesn't work
>  for running threads.  Worse, ptrace errors out claiming
>  the thread doesn't exits.
>
> - We must not stop all threads, obviously.
>
> - We must mark threads as running if we're resuming
>  them behind the core's back.
>
> - Implement target_stop_ptid to interrupt only one thread

I removed a bit of code that handled a SIGINT in sync_execution
with non-stop on, as that was something I'm not sure we want.

One issue I would like comments on, is that
-exec-continue / target_stop_ptid relies on an event happening
on the inferior.  Should we not rely on that, and just suspend
the thread with SIGSTOP ?  Would this affect frontends ?

-- 
Pedro Alves
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 010-non_stop_linux.diff
Type: text/x-diff
Size: 13827 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20080519/7c790e05/attachment.bin>