We have about a hundred engine stands controlled by qnx boxes, with a 10"
ethernet cable connected toWindows boxes. On a serial port this would be
called a null modem cable.
All data into and out of each box is done via sockets. The problem is that
when something goes wrong, there is no way to attach the remote debugger,
save going out to the lab and hooking up a temporary ethernet switch.
My question is, is it possible to create a debug pipe through the Windows
box, such that it simply echoes the byte stream that it receives in both
directions? I would have the Windows box listen on port 8000, and then
connect another socket to qnx on port 8000 upon accept(). This way I would
tell Momentix that it is to debug the Windows box, but it would actually be
debugging the qnx box through this pipe.
Robert Kindred
Oddly enough, the easiest way might actually be to use an
ssh tunnel. Assuming you’re running sshd on the QNX box
and have the authentication stuff set up properly,
ssh -f -N -l root -L 8000:localhost:8000 qnxbox
on the Windose box (in Cygwin, at least) should make its
port 8000 listen etc. in the way you want.
dB
“Robert Kindred” wrote ~ Fri, 4 Aug 2006 13:52:28 -0500:
We have about a hundred engine stands controlled by qnx boxes, with a 10"
ethernet cable connected toWindows boxes. On a serial port this would be
called a null modem cable.
All data into and out of each box is done via sockets. The problem is that
when something goes wrong, there is no way to attach the remote debugger,
save going out to the lab and hooking up a temporary ethernet switch.
My question is, is it possible to create a debug pipe through the Windows
box, such that it simply echoes the byte stream that it receives in both
directions? I would have the Windows box listen on port 8000, and then
connect another socket to qnx on port 8000 upon accept(). This way I would
tell Momentix that it is to debug the Windows box, but it would actually be
debugging the qnx box through this pipe.
Robert Kindred
\