QNX debugger

Gurus,

I am trying to figure out why the QDE debugger looses connection to the
target everytime after runnning perfectly fine for 5-10 minutes. Here’s
the setup that I have:

QDE running on x86 Host;
Target is another x86 machine;
Debugger connectivity: via qconn.

What could be wrong? The debugger shows “lost connection to target” even
though qconn is up and running on the target system. I am also able to
ping the target. And when I try to restart debugging, it fails with a
message saying cannot download the image in /tmp.

Tanmay.

Tanmay Kishore wrote:
I just forgot to mention that one of the directories on the target is NFS
mounted and I store all the executable image under this directory.
Apparently, the link to this directory goes down because even the
directory listing command “ls” does not work.

Does this give you guys any clue? I checked QNX documentation for
utilities like NFS and mount to see if there is any thing that can result
in a timeout and cause the link to go down. Unfortunately, I didn’t come
across any.

Tanmay.

Gurus,

I am trying to figure out why the QDE debugger looses connection to the
target everytime after runnning perfectly fine for 5-10 minutes. Here’s
the setup that I have:

QDE running on x86 Host;
Target is another x86 machine;
Debugger connectivity: via qconn.

What could be wrong? The debugger shows “lost connection to target” even
though qconn is up and running on the target system. I am also able to
ping the target. And when I try to restart debugging, it fails with a
message saying cannot download the image in /tmp.

Tanmay.

Tanmay Kishore wrote:

Tanmay Kishore wrote:
I just forgot to mention that one of the directories on the target is NFS
mounted and I store all the executable image under this directory.
Apparently, the link to this directory goes down because even the
directory listing command “ls” does not work.

Does this give you guys any clue? I checked QNX documentation for
utilities like NFS and mount to see if there is any thing that can result
in a timeout and cause the link to go down. Unfortunately, I didn’t come
across any.

Check the output of pidin. You might be able to see if any of the
processes involved such as io-net or fs-nfs* have gone down. You may
also be able to determine which processes are blocked on each other
which could give you clues as to what might be happening.

cheers,

Kris