Eclipse Community Forums: C / C++ IDE (CDT) » Diable Tread refresh in UI

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » Diable Tread refresh in UI

Show: Today's Messages :: Show Polls :: Message Navigator

Diable Tread refresh in UI [message #211884]

Thu, 13 March 2008 18:36

Ryan Hidek

Messages: 6
Registered: July 2009

Junior Member

My company has an application it needs to remotely debug using gdbserver
and Eclipse. Unfortunately, it has about 40 threads and takes an
exceedingly long time to step debug.
I'd like to modify the CDT plug-in to disable the constant thread status
updating (running/suspended, info threads, info sharedlibrary, etc) of all
the threads except the one being debugged.

Any ideas on where i need to make the modifications?
In the org.eclipse.cdt.debug.mi.core.cdi package?

Report message to a moderator

Re: Diable Tread refresh in UI [message #211946 is a reply to message #211884]

Fri, 14 March 2008 11:27

Eclipse User

Originally posted by: subs._nospam_consertum.com

Ryan Hidek wrote:
> My company has an application it needs to remotely debug using gdbserver
> and Eclipse. Unfortunately, it has about 40 threads and takes an
> exceedingly long time to step debug. I'd like to modify the CDT plug-in
> to disable the constant thread status updating (running/suspended, info
> threads, info sharedlibrary, etc) of all the threads except the one
> being debugged.
> Any ideas on where i need to make the modifications?
> In the org.eclipse.cdt.debug.mi.core.cdi package?
>
I'd start by placing breakpoints in CommandFactory (this is where all
the MI commands a created). You can then see where the required calls
are comming from.

HTH

--
Derek

Report message to a moderator

Re: Diable Tread refresh in UI [message #212036 is a reply to message #211884]

Tue, 18 March 2008 14:57

Ali Burak Kulakli

Messages: 116
Registered: July 2009

Senior Member

Hi,

I have a similar problem also. Any ideas what can I do as a user?

Burak

Ryan Hidek wrote:
> My company has an application it needs to remotely debug using gdbserver
> and Eclipse. Unfortunately, it has about 40 threads and takes an
> exceedingly long time to step debug. I'd like to modify the CDT plug-in
> to disable the constant thread status updating (running/suspended, info
> threads, info sharedlibrary, etc) of all the threads except the one
> being debugged.
> Any ideas on where i need to make the modifications?
> In the org.eclipse.cdt.debug.mi.core.cdi package?
>

Report message to a moderator

Re: Diable Tread refresh in UI [message #213188 is a reply to message #211946]

Tue, 01 April 2008 20:33

Ryan Hidek

Messages: 6
Registered: July 2009

Junior Member

So I tried stepping through the CDT code and from what i can see, it would
not be a trivial change to disable thread refreshing for all but the
thread you're interested in. Everything appears to be event driven and i
don't see an easy way to stop the events causing the other threads from
firing.

Anyone with more expertise on the issue able to shed some light on this?
I'm not 100% certain that it's not easily doable.

Report message to a moderator

Previous Topic:	Run CDT project from CLI?
Next Topic:	External Tool Builder isn't executed During manual build and auto build

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jul 21 16:17:00 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter