Eclipse Community Forums: C / C++ IDE (CDT)

Home » Language IDEs » C / C++ IDE (CDT) » Non-stop mode(How do all threads come to a halt on one breakpoint?)

Tue, 12 July 2016 09:17

Eclipse User

What exactly does Eclipse do when non-stop mode is not enabled ("all-stop" mode is enable) and all threads halt at one breakpoint?

Is GDB sending signals to other threads when a breakpoint is hit?

Re: Non-stop mode [message #1737850 is a reply to message #1737751]

Wed, 13 July 2016 09:51

Eclipse User

Really Eclipse isn't doing anything in "all-stop" mode as the modes are handled by GDB. All stop is how GDB has historically worked and non-stop is the new way. In All-stop, the process is stopped (all threads are stopped), in non-stop, the processes is not stopped, only the the thread with the breakpoint.

Some features in GDB are only supported when in non-stop mode, e.g. attaching additional processes (inferiors).

Have a look at the GDB docs: https://sourceware.org/gdb/onlinedocs/gdb/Thread-Stops.html#Thread-Stops

Previous Topic:	How to find filename and namespace in cdt ast node basespecifier (c++ inheritance)
Next Topic:	STlink-v2 - debug interface was not found (ft2232) - with Ubuntu and Openocd

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Aug 20 04:25:06 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter