mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-19 06:55:23 +02:00
dc77c1f3bb
The tests were relying on specific number of executable lines
in a function. However on some gdb/gcc combinations stopping
at a function stops at the line with the `{` and some
on the first line witin that function. Much of the tests
here assumed that latter. By using line tags we don't need
to worry about exact number of executable lines between entry
and area of interest. And by placing first line of code on
the same line as the opening `{` of the function, we can
have consistent stop locations when stepping into a function.
Part of #816
|
||
|---|---|---|
| .. | ||
| org.eclipse.cdt.dsf.gdb | ||
| org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui | ||
| org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui.tests | ||
| org.eclipse.cdt.dsf.gdb.tests | ||
| org.eclipse.cdt.dsf.gdb.ui | ||
| org.eclipse.cdt.examples.dsf.gdb | ||
| org.eclipse.cdt.gnu.dsf-feature | ||
| org.eclipse.cdt.gnu.multicorevisualizer-feature | ||
| org.eclipse.cdt.tests.dsf.gdb | ||
| pom.xml | ||