I am trying to debug with QNX 6.2.1A PE on a remote target. The target is a
Wintel (x86) machine and has the full Neutrino RTOS along with Momentics
installed on a QNX4 partition. The host is also another Wintel machine
running Monemtics under Windows XP.
In starting up the target for debugging, I isuue a qconn command in a
terminal window. I can the run a simple “Hello World” program (C/C++ QNX
QConn (IP)) successfully on the target from the host. However when I
attempt to run the same program as a debug progrma by using RUN/DEbug menu
selection, I get somewhat erratic behavour.
The option for the debugger under Launch Configurations is set to “Stop at
main() on startup” and “Run program in debugger” is selected as also is "QNX
GDB Debugger ". The C/C++ Application chosen to debug is the one with the
“_g” subfix. Upon clicking on the Debug button in the Launch Configurations
window, the source code is visible in the debug persepctive. Nothing is
shown within the console. The heading for the Conslole window shows
Console [QNX GDB Debugging (Suspended)].
In addition, the debug selections
Terminate
Suspend
Step Into
and Step Over
are all inactive.
In the “Hello World”, I have a for loop after the cout that outputs the
value of the counter i. If I set a breakpoint within that for loop, the same
results are seen as before. However if a breakpoint is placed on the first
executable statment that outputs the “Hello World”, the debug selections are
inactive but the Conslole window heading shows:
Console [QNX GDB Debugging (Breakpoint hit)].
The Target Navigator and the File system Navigator both seem to be working
fine with the target.
My questions are:
Is this a fair test for seeing if QNX remote debugger can operate
correctly?
Is there a way to get the QNX remote debugger to work that I might be
overlooking?
I am trying to debug with QNX 6.2.1A PE on a remote target. The target is
a
Wintel (x86) machine and has the full Neutrino RTOS along with Momentics
installed on a QNX4 partition. The host is also another Wintel machine
running Monemtics under Windows XP.
In starting up the target for debugging, I isuue a qconn command in a
terminal window. I can the run a simple “Hello World” program (C/C++ QNX
QConn (IP)) successfully on the target from the host. However when I
attempt to run the same program as a debug progrma by using RUN/DEbug menu
selection, I get somewhat erratic behavour.
The option for the debugger under Launch Configurations is set to “Stop at
main() on startup” and “Run program in debugger” is selected as also is
"QNX
GDB Debugger ". The C/C++ Application chosen to debug is the one with the
“_g” subfix. Upon clicking on the Debug button in the Launch
Configurations
window, the source code is visible in the debug persepctive. Nothing is
shown within the console. The heading for the Conslole window shows
Console [QNX GDB Debugging (Suspended)].
In addition, the debug selections
Terminate
Suspend
Step Into
and Step Over
are all inactive.
In the “Hello World”, I have a for loop after the cout that outputs the
value of the counter i. If I set a breakpoint within that for loop, the
same
results are seen as before. However if a breakpoint is placed on the
first
executable statment that outputs the “Hello World”, the debug selections
are
inactive but the Conslole window heading shows:
Console [QNX GDB Debugging (Breakpoint hit)].
The Target Navigator and the File system Navigator both seem to be working
fine with the target.
My questions are:
Is this a fair test for seeing if QNX remote debugger can operate
correctly?
Is there a way to get the QNX remote debugger to work that I might be
overlooking?
As it turns out, the Debug window was not active in the Debug persepctive (I
am a newbie to QNX and did not know any better). Once I placed a Debug view
in the Debug persepctive the debugger seemed to work normal. Removing the
Debug view from the Debug perspective caused the problem previously
described.
Seems a bit strange to me that the Debug view is so important to have up.
The only thing that might be unusual is that I noticed that the Terminate at
the menu /Debug/Terminate is not active. The “Step Into”, “Step Over”, and
“Resume” are active.
I am trying to debug with QNX 6.2.1A PE on a remote target. The target
is
a
Wintel (x86) machine and has the full Neutrino RTOS along with Momentics
installed on a QNX4 partition. The host is also another Wintel machine
running Monemtics under Windows XP.
In starting up the target for debugging, I isuue a qconn command in a
terminal window. I can the run a simple “Hello World” program (C/C++ QNX
QConn (IP)) successfully on the target from the host. However when I
attempt to run the same program as a debug progrma by using RUN/DEbug
menu
selection, I get somewhat erratic behavour.
The option for the debugger under Launch Configurations is set to “Stop
at
main() on startup” and “Run program in debugger” is selected as also is
"QNX
GDB Debugger ". The C/C++ Application chosen to debug is the one with
the
“_g” subfix. Upon clicking on the Debug button in the Launch
Configurations
window, the source code is visible in the debug persepctive. Nothing is
shown within the console. The heading for the Conslole window shows
Console [QNX GDB Debugging (Suspended)].
In addition, the debug selections
Terminate
Suspend
Step Into
and Step Over
are all inactive.
In the “Hello World”, I have a for loop after the cout that outputs the
value of the counter i. If I set a breakpoint within that for loop, the
same
results are seen as before. However if a breakpoint is placed on the
first
executable statment that outputs the “Hello World”, the debug selections
are
inactive but the Conslole window heading shows:
Console [QNX GDB Debugging (Breakpoint hit)].
The Target Navigator and the File system Navigator both seem to be
working
fine with the target.
My questions are:
Is this a fair test for seeing if QNX remote debugger can operate
correctly?
Is there a way to get the QNX remote debugger to work that I might
be
overlooking?
As it turns out, the Debug window was not active in the Debug persepctive
(I
am a newbie to QNX and did not know any better). Once I placed a Debug
view
in the Debug persepctive the debugger seemed to work normal. Removing the
Debug view from the Debug perspective caused the problem previously
described.
Seems a bit strange to me that the Debug view is so important to have up.
The only thing that might be unusual is that I noticed that the Terminate
at
the menu /Debug/Terminate is not active. The “Step Into”, “Step Over”, and
“Resume” are active.
Thanks Mikhail for asking about the Debug view…
regards,
james jenkins
“Mikhail Khodjaiants” <> mikhailk@qnx.com> > wrote in message
news:bksa4e$3af$> 1@nntp.qnx.com> …
What is in the “Debug” view? Can you see threads, stack frames?
I am trying to debug with QNX 6.2.1A PE on a remote target. The
target
is
a
Wintel (x86) machine and has the full Neutrino RTOS along with
Momentics
installed on a QNX4 partition. The host is also another Wintel
machine
running Monemtics under Windows XP.
In starting up the target for debugging, I isuue a qconn command in a
terminal window. I can the run a simple “Hello World” program (C/C++
QNX
QConn (IP)) successfully on the target from the host. However when I
attempt to run the same program as a debug progrma by using RUN/DEbug
menu
selection, I get somewhat erratic behavour.
The option for the debugger under Launch Configurations is set to
“Stop
at
main() on startup” and “Run program in debugger” is selected as also
is
"QNX
GDB Debugger ". The C/C++ Application chosen to debug is the one with
the
“_g” subfix. Upon clicking on the Debug button in the Launch
Configurations
window, the source code is visible in the debug persepctive. Nothing
is
shown within the console. The heading for the Conslole window shows
Console [QNX GDB Debugging (Suspended)].
In addition, the debug selections
Terminate
Suspend
Step Into
and Step Over
are all inactive.
In the “Hello World”, I have a for loop after the cout that outputs
the
value of the counter i. If I set a breakpoint within that for loop,
the
same
results are seen as before. However if a breakpoint is placed on the
first
executable statment that outputs the “Hello World”, the debug
selections
are
inactive but the Conslole window heading shows:
Console [QNX GDB Debugging (Breakpoint hit)].
The Target Navigator and the File system Navigator both seem to be
working
fine with the target.
My questions are:
Is this a fair test for seeing if QNX remote debugger can operate
correctly?
Is there a way to get the QNX remote debugger to work that I might
be
overlooking?