Why can't I debug with the Momentics IDE

I have never been able to get debugging working with the IDE. Up to now I have simply been debugging with CLI gdb (which I like just
fine), but I would like the IDE debugger to work (mostly because it irritates me). What am I doing wrong.

  • This is with 6.2.1A.
  • I am running qconn
  • The following is the log that is produced

!ENTRY org.eclipse.debug.ui 4 120 Dec 23, 2003 09:03:18.246
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing: No Target

Stack trace:
java/lang/Throwable.()V
java/lang/Throwable.(Ljava/lang/String;)V
org/eclipse/cdt/debug/core/cdi/CDIException.(Ljava/lang/String;)V

com/qnx/tools/ide/qde/debug/internal/core/CGDBDebugger.createAttachSession(Lorg/eclipse/debug/core/ILaunchConfiguration;Lorg/eclipse/core/resources/IFile;I)Lorg/eclipse/cdt/debug/core/cdi/ICDISes

org/eclipse/cdt/launch/internal/LocalCLaunchConfigurationDelegate.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/I

org/eclipse/debug/internal/core/LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;
org/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationDialog$10.run(Lorg/eclipse/core/runtime/IProgressMonitor;)V
org/eclipse/jface/operation/ModalContext$ModalContextThread.run()V

!ENTRY org.eclipse.cdt.launch 4 150 Dec 23, 2003 09:03:18.250
!MESSAGE Failed Launching CDI Debugger : Error initializing: No Target
!STACK 0
org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing: No Target

Stack trace:
java/lang/Throwable.()V
java/lang/Throwable.(Ljava/lang/String;)V
org/eclipse/cdt/debug/core/cdi/CDIException.(Ljava/lang/String;)V

com/qnx/tools/ide/qde/debug/internal/core/CGDBDebugger.createAttachSession(Lorg/eclipse/debug/core/ILaunchConfiguration;Lorg/eclipse/core/resources/IFile;I)Lorg/eclipse/cdt/debug/core/cdi/ICDISes

org/eclipse/cdt/launch/internal/LocalCLaunchConfigurationDelegate.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/I

org/eclipse/debug/internal/core/LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;
org/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationDialog$10.run(Lorg/eclipse/core/runtime/IProgressMonitor;)V
org/eclipse/jface/operation/ModalContext$ModalContextThread.run()V

Do you have pdebug on the target system?


Malte

“Rennie Allen” <rallen@csical.com> schrieb im Newsbeitrag
news:bs9rp8$81u$1@inn.qnx.com

I have never been able to get debugging working with the IDE. Up to now I
have simply been debugging with CLI gdb (which I like just
fine), but I would like the IDE debugger to work (mostly because it
irritates me). What am I doing wrong.

  • This is with 6.2.1A.
  • I am running qconn
  • The following is the log that is produced

!ENTRY org.eclipse.debug.ui 4 120 Dec 23, 2003 09:03:18.246
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing: No Target

Stack trace:
java/lang/Throwable.()V
java/lang/Throwable.(Ljava/lang/String;)V

org/eclipse/cdt/debug/core/cdi/CDIException.(Ljava/lang/String;)V


com/qnx/tools/ide/qde/debug/internal/core/CGDBDebugger.createAttachSession(L

org/eclipse/debug/core/ILaunchConfiguration;Lorg/eclipse/core/resources/IFil
e;I)Lorg/eclipse/cdt/debug/core/cdi/ICDISes

org/eclipse/cdt/launch/internal/LocalCLaunchConfigurationDelegate.launch(Lor

g/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/deb
ug/core/ILaunch;Lorg/eclipse/core/runtime/I

org/eclipse/debug/internal/core/LaunchConfiguration.launch(Ljava/lang/String

;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch
;

org/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationDialog

$10.run(Lorg/eclipse/core/runtime/IProgressMonitor;)V

org/eclipse/jface/operation/ModalContext$ModalContextThread.run()V

!ENTRY org.eclipse.cdt.launch 4 150 Dec 23, 2003 09:03:18.250
!MESSAGE Failed Launching CDI Debugger : Error initializing: No Target
!STACK 0
org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing: No Target

Stack trace:
java/lang/Throwable.()V
java/lang/Throwable.(Ljava/lang/String;)V

org/eclipse/cdt/debug/core/cdi/CDIException.(Ljava/lang/String;)V


com/qnx/tools/ide/qde/debug/internal/core/CGDBDebugger.createAttachSession(L

org/eclipse/debug/core/ILaunchConfiguration;Lorg/eclipse/core/resources/IFil
e;I)Lorg/eclipse/cdt/debug/core/cdi/ICDISes

org/eclipse/cdt/launch/internal/LocalCLaunchConfigurationDelegate.launch(Lor

g/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/deb
ug/core/ILaunch;Lorg/eclipse/core/runtime/I

org/eclipse/debug/internal/core/LaunchConfiguration.launch(Ljava/lang/String

;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch
;

org/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationDialog

$10.run(Lorg/eclipse/core/runtime/IProgressMonitor;)V

org/eclipse/jface/operation/ModalContext$ModalContextThread.run()V

Malte Mundt wrote:

Do you have pdebug on the target system?

Thanks for responding.

If you are wondering whether I have the pdebug executable on the “target” the answer is yes. The “target” is a QNX PE development
system (I am running eclipse on QNX), and I had qconn running, at the time of the above exception.

Rennie

Rennie Allen wrote:

Malte Mundt wrote:

Do you have pdebug on the target system?


Thanks for responding.

If you are wondering whether I have the pdebug executable on the
“target” the answer is yes. The “target” is a QNX PE development system
(I am running eclipse on QNX), and I had qconn running, at the time of
the above exception.

OK, I am the first to answer my own question in the new newsgroups :slight_smile:

The problem appears to have been one of memory. I increased the RAM in
my system to 384MB and it seems to work. Although it appears that the
gui debugger is completely useless for doing any kind real-time work,
since if the priority of any of the threads is higher than normal, the
gui is not responsive (I can debug the exact application using gdb at
the command line setting exactly the same breakpoints, etc. without
any problem at all).

Rennie

OK, I am the first to answer my own question in the new newsgroups > :slight_smile:

The problem appears to have been one of memory. I increased the RAM in
my system to 384MB and it seems to work. Although it appears that the
gui debugger is completely useless for doing any kind real-time work,
since if the priority of any of the threads is higher than normal, the
gui is not responsive (I can debug the exact application using gdb at
the command line setting exactly the same breakpoints, etc. without
any problem at all).

I have a 2.4G PC running with 256MB RAM under Windows 2000,
and debug is just on the other(bad) side of tolerable.
Single stepping takes 3-5 seconds per step, even if there
are the two perspectives open: C & debug.

As an aside-what happens if you run pdebug at a higher
priority? (Although with the floating nature of priorities
with QNX6, I guess it would be very difficult to get it
stay at the higher priority)

acellarius@yahoo.com wrote:

I have a 2.4G PC running with 256MB RAM under Windows 2000,
and debug is just on the other(bad) side of tolerable.
Single stepping takes 3-5 seconds per step, even if there
are the two perspectives open: C & debug.

Yeah, it seems that the problem is that the IDE runs some
threads at a priority below my lowest priority thread, which
runs at priority 8 on my system, and consumes a fair amount
of cpu time (although not all). Using command line debugger
seems to have no problem since it runs at shell prio.

None of this is a big deal for me personally, since I am
happy and productive with command line gdb, but I can’t
imagine how anyone can actually use the IDE native for
debugging real-time apps…

As an aside-what happens if you run pdebug at a higher
priority? (Although with the floating nature of priorities
with QNX6, I guess it would be very difficult to get it
stay at the higher priority)

Haven’t tried it. As I said, I can see j9 threads below the
priority of my lowest prio thread, so I am assuming that is
the cause of the problem.

Rennie