[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] ETA on new source file lookup scheme?
|
At the moment the switching to the Eclipse Source Lookup Framework is almost
done though hasn't been committed. But this will not affect the source
search mechanism, only the UI. When the switch is completed we are planning
to revisit the CDT breakpoint setting scheme. This work was scheduled for
M6, but has been postponed.
The automatic source search is still problematic. You always mention that
gdb (and Insight) knows the full paths. Yes indeed, it does, but it keeps it
internally. Some debug formats include the compilation paths, but I don't
know how to extract this information from gdb. So the user still needs to
specify the search paths.
Moreover, if you have two files with the same name in you project gdb often
gets confused.
----- Original Message -----
From: "Øyvind Harboe" <oyvind.harboe@xxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Wednesday, April 13, 2005 4:24 AM
Subject: [cdt-debug-dev] ETA on new source file lookup scheme?
I find myself returning to Insight intermittantly because it still has
an edge w.r.t. automatically looking source files. Typically this is
when debugging e.g. runtime libraries in the GCC compiler.
I thought about making another round of changes to the Zylin Embedded
CDT plugin, but if the new source file lookup scheme is just around the
corner...
--
Øyvind Harboe
http://www.zylin.com
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
