This is the mail archive of the
mailing list for the Archer project.
Re: BUG? gdb, non-stop && c -a
> non-stop mode should be generally used together with:
> (gdb) set target-async on
IMHO if gdb confuses itself without these settings being in lock-step,
there should only be one setting.
> > 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.
Now that's just a bug. Even if known and intended in the code,
it's clearly a misfeature from any sensible user perspective.