I have a debug build of some code that I’m trying to run on a remote target
from the IDE. I get the following message and then the IDE hangs. I have to
quit the IDE. The release build works fine by transfering to the target and
executing from command line.
Other simple .cpp programs also work via remote debug from the IDE, this
build is more complex but doesn’t include any specific QNX calls ie. no
multithreading, just generic cpp and compiles with no warnings.
If I copy file_g to the remote machine I can telnet to the remote machine
and run the file_g from gdb on the command line. I can then step over and
into the file as expected.
If gdb from command line can do this why can’t the IDE do the same, I’m
using the same execuatble in both cases. An IDE bug ??
I have a debug build of some code that I’m trying to run on a remote
target
from the IDE. I get the following message and then the IDE hangs. I have
to
quit the IDE. The release build works fine by transfering to the target
and
executing from command line.
Other simple .cpp programs also work via remote debug from the IDE, this
build is more complex but doesn’t include any specific QNX calls ie. no
multithreading, just generic cpp and compiles with no warnings.