> I'm having a problem debugging in gdb. It seems that when I press CTRL-C
> to interrupt the program, gdb suspends or stops EVERY thread (of which
> there are quite a few). When I type 'c' or 'continue', execution resumes
> for that thread only. This means I must type c ( and return of course )
> many times, which is no one's idea of fun. Searching the documentation,
> I found out that you can apply a command to a list of threads. So I do:
The cntrl-c should stop all threads (that is gdb's current thread
model). The continue, however, should have continued all threads - that
not happening sounds like a target dependant bug.
If anyone (else) is to get any further with this, the host/target and
other information are going to be useful.
enjoy,
Andrew
> thread apply all continue
>
> to apply the command 'continue' to all threads.
> But instead of resuming execution, I get (after several succesful
> 'continues' on some threads:
>
> ptrace in stop_thread: Operation not permitted.
>
> for one particular thread.
>
> What's going on here?
_______________________________________________
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
