Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Debugging Problems
Debugging Problems [message #152232] Wed, 24 August 2005 20:37 Go to next message
Eclipse UserFriend
Originally posted by: ozbod_333.hotmail.com

Hi all,

I am trying to use CDT3.0 on Linux AS3.0 with GDB 5.3.90-0.20030710.40rh to
debug a multi-threaded application
that makes numerous calls to shared libraries. I am having a number of
issues with the debugger under CDT which I am
not having if I run 'ddd' which is strange as both tools sit on top of
GDB??.

Problem 1: The CDT debugger refuses to see the source code for a given
shared library. I have added all the paths and
locations as required but still it won't let me step into that area of code.
'ddd' finds all the code fine without having to setup
a single thing.

Problem 2: The application is multithreaded and when I allow the application
to run on and create all the threads the
debugger won't stop on any breakpoint even though I know the threads are
accessing some of the methods with bp's
and then eventually cannot 'attach' to the thread and get any info at all,
i.e. I cannot even get the debugger to pause
the thread. Again all the above can be done fine with 'ddd'.

Our organisation is really keen to adopt Eclipse and CDT as our defacto C++
development IDE but it is hard to
convince people when it cannot perform as well as other (non-integrated)
tools such as 'ddd'. Thus any help anyone
can give in overcoming the above problems would be greatly appreciated.

Cheers,

ozbod
Re: Debugging Problems [message #152289 is a reply to message #152232] Thu, 25 August 2005 11:58 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mikhailk.qnx.com

> Problem 1: The CDT debugger refuses to see the source code for a given
> shared library. I have added all the paths and
> locations as required but still it won't let me step into that area of
> code. 'ddd' finds all the code fine without having to setup
> a single thing.

The CDT debugger doesn't block stepping into a library. It simply sends the
"step" command to gdb. There could be different reasons why gdb can not step
into a function, but I don't think the source lookup path is one of them.
The source lookup is performed after the step operation is accomplished.

> Problem 2: The application is multithreaded and when I allow the
> application to run on and create all the threads the
> debugger won't stop on any breakpoint even though I know the threads are
> accessing some of the methods with bp's
> and then eventually cannot 'attach' to the thread and get any info at all,
> i.e. I cannot even get the debugger to pause
> the thread. Again all the above can be done fine with 'ddd'.
>

I can only guess that the breakpoints are not set correctly. When you start
a debug session , the debugger tries to identify the breakpoints that belong
to the program being debugged. The source lookup path is used for these
purposes. If a breakpoint is set to the debug session the breakpoint's image
contains a check mark.

"exquisitus" <ozbod_333@hotmail.com> wrote in message
news:dej3su$61t$1@news.eclipse.org...
> Hi all,
>
> I am trying to use CDT3.0 on Linux AS3.0 with GDB 5.3.90-0.20030710.40rh
> to debug a multi-threaded application
> that makes numerous calls to shared libraries. I am having a number of
> issues with the debugger under CDT which I am
> not having if I run 'ddd' which is strange as both tools sit on top of
> GDB??.
>
> Problem 1: The CDT debugger refuses to see the source code for a given
> shared library. I have added all the paths and
> locations as required but still it won't let me step into that area of
> code. 'ddd' finds all the code fine without having to setup
> a single thing.
>
> Problem 2: The application is multithreaded and when I allow the
> application to run on and create all the threads the
> debugger won't stop on any breakpoint even though I know the threads are
> accessing some of the methods with bp's
> and then eventually cannot 'attach' to the thread and get any info at all,
> i.e. I cannot even get the debugger to pause
> the thread. Again all the above can be done fine with 'ddd'.
>
> Our organisation is really keen to adopt Eclipse and CDT as our defacto
> C++ development IDE but it is hard to
> convince people when it cannot perform as well as other (non-integrated)
> tools such as 'ddd'. Thus any help anyone
> can give in overcoming the above problems would be greatly appreciated.
>
> Cheers,
>
> ozbod
>
Re: Debugging Problems [message #152335 is a reply to message #152232] Fri, 26 August 2005 02:44 Go to previous message
Eclipse UserFriend
Originally posted by: grkoma.nospamgmail.com

Hello,

I had similar problem some time ago, try to set source lookup path. If
it is not set correctly, breakpoints are showed in editor, but debugger
wont stop on it. Setting source lookup path will solve this problem.

Marko


exquisitus wrote:
> Hi all,
>
> I am trying to use CDT3.0 on Linux AS3.0 with GDB 5.3.90-0.20030710.40rh to
> debug a multi-threaded application
> that makes numerous calls to shared libraries. I am having a number of
> issues with the debugger under CDT which I am
> not having if I run 'ddd' which is strange as both tools sit on top of
> GDB??.
>
> Problem 1: The CDT debugger refuses to see the source code for a given
> shared library. I have added all the paths and
> locations as required but still it won't let me step into that area of code.
> 'ddd' finds all the code fine without having to setup
> a single thing.
>
> Problem 2: The application is multithreaded and when I allow the application
> to run on and create all the threads the
> debugger won't stop on any breakpoint even though I know the threads are
> accessing some of the methods with bp's
> and then eventually cannot 'attach' to the thread and get any info at all,
> i.e. I cannot even get the debugger to pause
> the thread. Again all the above can be done fine with 'ddd'.
>
> Our organisation is really keen to adopt Eclipse and CDT as our defacto C++
> development IDE but it is hard to
> convince people when it cannot perform as well as other (non-integrated)
> tools such as 'ddd'. Thus any help anyone
> can give in overcoming the above problems would be greatly appreciated.
>
> Cheers,
>
> ozbod
>
>
Previous Topic:Why code completion is so slow?
Next Topic:Export workspace/projects settings ?
Goto Forum:
  


Current Time: Thu Jul 17 04:32:02 EDT 2025

Powered by FUDForum. Page generated in 0.30895 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top