RE: [cdt-dev] EclipseCDT debugging -> too slow

[Thomas Fletcher <ThomasF@xxxxxxx>]

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Bu Bacoo
> Sent: Friday, April 21, 2006 6:48 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] EclipseCDT debugging -> too slow
> 
> Hello
> 
> I'd like to ask you about your experience and opinions. From 
> my point of view, debugging a C++ program in Eclipse/CDT is too slow. 
> 
> E.g. jumping into inherited constructor takes 1-2 seconds, 
> method calls and switching to other source, again some seconds... 
> 
> I'm running 3.1.0.200604171607, but it was so also in 
> 3.0.1something... I have tried moving from Blackdown jvm to 
> SUN's (1.5), but nothing big changed, maybe a little speedup.
> 
> I'm running on 2GHz centrino with 1G Ram, so that should be 
> no problem. On MS windows it runs somewhat faster, but maybe 
> that is also just a feeling. 
> 
> Any way to speed it up? Hope Intel's Core DUO and 4G ram is 
> not the only way. For example, I can see 10 of 40M heap size, 
> maybe extending it? Or?

How does it perform compared to doing the same operations at the 
GDB (assuming you are using GDB) level?  There is definitely a 
larger overhead associated with synchronizing multiple data sources
(ie continuous display of backtrace, shared object states, registers
etc) that you don't have when running gdb that responds to a step
with (unless otherwise configured)

(gdb) 

Thomas