This is the mail archive of the mailing list for the Archer project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BUG? gdb, non-stop && c -a

On 07/20, Jan Kratochvil wrote:
> 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

Hmm, thanks... I'll read the docs about target-async.

> > 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?

But doesn't list all threads? p4745.4746 is the single thread?

And, in any case, gdbserver resumes only this thread.

> > 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.

OK, thanks.

So, it is not possible to enter the CLI mode again after "c -a" ?
(unless the target hits the bp or something, of course).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]