[cdt-debug-dev] Re: cdt-debug-dev digest, Vol 1 #296 - 3 msgs

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

> Does it mean we replace gdb/Insight as your number #1 debugger ?

Not yet.

Insight is very much still in the game. 

Mainly it scores over CDT when dealing with runtime libraries that are
compiled outside Eclipse projects and highly optimised code(basically
CDT trusts the information it is served from GDB + debug info too much).
In my case that's mainly eCos OS + STLport. 

Secondly Insight tends to score over CDT when debugging hardware
problems. When the hardware doesn't work, the earth moves under CDT's
feet and CDT tends to fall over when it is making assumptions and
building upon those assumptions.

Finally it is worthwhile mentioning that CDT and Insight does not have
the same set of bugs, so when CDT breaks Insight comes in handy. 

To become my embedded debugger of choice, more bugs must be fixed, the
GDB console must become a first class citizen and the Eclipse OS != GCC
host OS path problems must be addressed(actually I've maimed CDT to fix
the last point).


-- 
Øyvind Harboe
http://www.zylin.com