Only once they are loaded, this is a big one IMO, it really hurts my
day to day work on Linux and Windows. On Mac this is less a problem
since they are loaded at the same time of the executable symbols (well,
except for dlopened).
On 10-04-09 1:30 PM, Doug Schaefer wrote:
ouch. that's actually a huge one. Without it, you can't
set breakpoints in shared libraries, no?
On Fri, Apr 9, 2010 at 11:58 AM, Marc
Khouzam <marc.khouzam@xxxxxxxxxxxx>
wrote:
So we do have a parity issue.
I'll add it back to the list.
On Thu, Apr 8, 2010 at 9:59 AM, Marc
Khouzam <marc.khouzam@xxxxxxxxxxxx>
wrote:
> > Let us know if you have any other issues.
> Well, the missing support for pending breakpoints
certainly
> needs fixing ... ;-)
Yes, this one is a popular one (it even has 4 votes).
Although, as per
http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg17353.html
(copied below)
it is not a feature-parity problem because CDI doesn't do it either :-)
That's actually a semantically incorrect statement. The
CDI/MI integration implemented it's own pending breakpoint solution
attempting to set breakpoints on every shared library load event. If
DSF/GDB does that too, then I'd say you have parity.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|