Eclipse Community Forums: C / C++ IDE (CDT) » Disabling thread info on each step

Home » Language IDEs » C / C++ IDE (CDT) » Disabling thread info on each step

Disabling thread info on each step [message #59594]

Thu, 23 January 2003 12:03

Eclipse User

Originally posted by: goran.pantar.xylon.hr

Hi

I think that it would be good to disable thread info on each step during
debugging. Command "info threads" is slowing down debugging. It would be
best to have thread information as option in separate window.
Also command "info sharedlibrary" is not accepted by my mips-elf-gdb, so
is there any way to avoid issuing that command (Check box in debugger menu
"Automatically load shared libraries" doesn't make any difference).

thank you

goran

Re: Disabling thread info on each step [message #59639 is a reply to message #59594]

Thu, 23 January 2003 13:30

Eclipse User

Originally posted by: mikhailk.qnx.com

"Goran Pantar" <goran.pantar@xylon.hr> wrote in message
news:b0p79m$hbm$1@rogue.oti.com...
> Hi
>
> I think that it would be good to disable thread info on each step during
> debugging. Command "info threads" is slowing down debugging. It would be
> best to have thread information as option in separate window.

Unfortunately, gdb/mi doesn't support notifications for threads and shared
libraries. To check if some thread is created or detroyed during the steping
we have to use commands as 'info threads'. Same is for shared libraries.

> Also command "info sharedlibrary" is not accepted by my mips-elf-gdb, so
> is there any way to avoid issuing that command (Check box in debugger menu
> "Automatically load shared libraries" doesn't make any difference).

The issues related to shared libraries are new and still are "under
construction". We will make it optional.
The 'Automatically load shared libraries' option is not supported by cygwin
gdb and has to be removed from the page if 'CygwinGDBDebugger' is selected.

>
> thank you
>
> goran
>

Re: Disabling thread info on each step [message #61043 is a reply to message #59639]

Mon, 03 February 2003 19:48

Eclipse User

Originally posted by: alain.no.spam

Mikhail Khodjaiants wrote:

> "Goran Pantar" <goran.pantar@xylon.hr> wrote in message
> news:b0p79m$hbm$1@rogue.oti.com...
> > Hi
> >
> > I think that it would be good to disable thread info on each step during
> > debugging. Command "info threads" is slowing down debugging. It would be
> > best to have thread information as option in separate window.

> Unfortunately, gdb/mi doesn't support notifications for threads and shared
> libraries. To check if some thread is created or detroyed during the steping
> we have to use commands as 'info threads'. Same is for shared libraries.

And to add to Mikhailks comments.
Gdb sends notification for thread creation, but ...
- they are platform dependent
- do not follow any specific formats
- and we still do not know when a thread is terminated.

> > Also command "info sharedlibrary" is not accepted by my mips-elf-gdb, so
> > is there any way to avoid issuing that command (Check box in debugger menu
> > "Automatically load shared libraries" doesn't make any difference).

> The issues related to shared libraries are new and still are "under
> construction". We will make it optional.
> The 'Automatically load shared libraries' option is not supported by cygwin
> gdb and has to be removed from the page if 'CygwinGDBDebugger' is selected.

Done, UI/control remove for CygwinGDBDebugger.

Maybe we could had a preference to disable the automatic
update of the the managers, but it may severely infere with
the UI framework wich relies on those notifications to
supply infos to the user..

> >
> > thank you
> >
> > goran
> >

Previous Topic:	about C/C++ rebuild
Next Topic:	Code Completion on W2K

Goto Forum:

-=] Back to Top [=-

Current Time: Sun May 11 04:23:24 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter