This is the mail archive of the
mailing list for the Archer project.
Re: BUG? gdb, non-stop && c -a
On Tue, 20 Jul 2010 16:01:36 +0200, Oleg Nesterov wrote:
> On 07/20, Oleg Nesterov wrote:
> > Using the same test-case, I did
> Another oddity. Again, the same test-case but I guess any mt program
> can be used.
> (gdb) set non-stop
non-stop mode should be generally used together with:
(gdb) set target-async on
> this sends "vCont;c:p4745.4746" but not "vCont;c:p4745.-1" as I'd expect.
Why is this a problem to list all the threads instead of -1?
> Now it sends "vCont;c:p4745.4745" and resumes the main thread. But
> now gdb doesn't react to ^C and "hangs". (no, SIGINT is not blocked).
CTRL-C is not useful in target-async mode.