| Re: [cdt-dev] Should gdb default non-stop mode debugging? |
|
Just to make sure I understand: All-stop: means that all threads will stop whenever one stops (when a breakpoint hits for example) Non-stop: threads can be stopped individually, (when a breakpoint hits the other threads continue)
Aside from that, are there any differences (benefits?) to non-stop vs all-stop?
Things I know of: - Reverse debugging does not work with non-stop - Debug forked processes does not work with all-stop
One thing to consider if the default is changed: existing launch configs with Reverse debugging turned on will break. Right? I think it would be good if things could be a bit more automatic so that the user gets the best experience by default, i.e. non-stop if available, etc.
Marc-André From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Sent: Tuesday, January 31, 2017 1:41:32 PM To: CDT General developers list. Subject: Re: [cdt-dev] Should gdb default non-stop mode debugging? Windows and Mac don't support non-stop. Specific embedded targets also may not support non-stop.
There is a preferences C/C++->Debug->GDB => "Non-stop mode" that the user can enable so that non-stop is selected by defaultfor each new launch.
All-stop works all the time.
So, although I always run non-stop, it is probably safer to leave
the default to all-stop, and let users that understand the difference
enable it.
Marc
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Jeff Johnston <jjohnstn@xxxxxxxxxx>
Sent: January 31, 2017 13:35 To: CDT General developers list. Subject: [cdt-dev] Should gdb default non-stop mode debugging? Is there any reason for not defaulting the CDT debugger to use non-stop debugging these days (i.e.
are there known gdb implementations out there supported by CDT that don't support non-stop mode)? If there are good reasons, should the default be based on the gdb version or platform? This came up as a Fedora bug so I thought I would ask the CDT Debug experts to see if the default is set the way it is for more than historical reasons. -- Jeff J. _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
| ||