Hi,
I have Momentix 2.0 on a Windows XP machine. The target machine is a
(stripped) QNX 6.3.0 machine. When I want to do remote debugging I
have a slow debug-startup. This means uploading the executable is ok
but then I have to wait for a couple of minutes before I reach
main(). What I see is Thread[1] (running). I have noticed that at
this moment pdebug is communicating with Momentix using TCP. After
about 6.4 Mb to the QNX machine and about 3.5 Mb to Momentix the
main() is reached and I can start debugging.
When my target machine is a complete 6.3.2 machine debugging works
fine.
Does anyone know what is missing on my QNX 6.3.0 machine?
Regards,
Richard
Sounds like you have mismatched versions - the host must be 6.3.0 too (switch
with qwincfg)
The reason this affects things is that the debugger sets a breakpoint
inside libc for detecting shared libs being loaded. If the libc.so on the
target doesn’t match then it could be set in the wrong place, and often this
goes into the symbol resolution code, which will cause things to take forever
to get to main. I’m surprised you waited that long actually! 
Sometimes it may even cause your target program to crash!
RichardVerzijl wrote:
Hi,
I have Momentix 2.0 on a Windows XP machine. The target machine is a
(stripped) QNX 6.3.0 machine. When I want to do remote debugging I
have a slow debug-startup. This means uploading the executable is ok
but then I have to wait for a couple of minutes before I reach
main(). What I see is Thread[1] (running). I have noticed that at
this moment pdebug is communicating with Momentix using TCP. After
about 6.4 Mb to the QNX machine and about 3.5 Mb to Momentix the
main() is reached and I can start debugging.
When my target machine is a complete 6.3.2 machine debugging works
fine.
Does anyone know what is missing on my QNX 6.3.0 machine?
Regards,
Richard
–
cburgess@qnx.com