This is the mail archive of the archer@sourceware.org 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: gdbstub initial code, v9


>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> I would find non-stop as a more general solution.  In non-stop mode
Jan> one still can stop each and all the threads manually.  But in
Jan> all-stop mode one cannot keep the (other) threads running.
[...]
Jan> all-stop mode could be also emulated probably from the GDB client side.

I thought Pedro talked about this once, but I can't find the message.

This seems like a reasonable future project for us -- it seems to me
that if ugdb does the thread-specific stop filtering, then it would make
sense to notify it of thread-specific breakpoints, and then always use
non-stop.

Tom


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