Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
IDE/Discussion/General/Debugging : Target Request Failed: Target is not responding /List of Posts
Forum Topic - Debugging : Target Request Failed: Target is not responding : (9 Items)
   
Update
Lakshmi Teeka(deleted)
12/30/2009 1:52 AM
post44451
Debugging : Target Request Failed: Target is not responding   
Hello All,

I have QNX SDP 6.4.1 installed on Ubuntu-Linux 9.04 host machine.
I have VMWare Player  - Virtual Machine installed with  QNX 6.4.1.

I perform the following to do debugging of my application.

1. Launch my sample application as a background process in vmware target of qnx641
2. Launch the debug configuration configured for "Attach to process thro' Qconn".
3. The source path, shared library path all are set.
4. The debugger launches. But if I click the button to start debugging, getting an error
"Target Request Failed: Target is not Responding"

Can somebody point me where I am going wrong? Do I need to apply any patches?

Thanks
Lakshmi
Dave Bott(deleted)
12/30/2009 11:20 AM
post44459
RE: Debugging : Target Request Failed: Target is not responding   
Does the QNX target have an IP address assigned to it ? Run 'ifconfig' on the target and see. The defaults are to use 
dhcp, so most vmware configurations should work, but it's an easy thing to check. If that's set, can you ping the target
 from the host ? If so, you have a good network connection.
 
Most likely, you have not started 'qconn' - it is not enabled by default after installation. You can add a line:
qconn
to /etc/rc.d/r.local
to enable it every time your system boots.
You can also start inetd by adding a line:
inetd
to the same file - then enable services like ftp and telnet in /etc/inetd.conf
 
If qconn is running, you should be able to see the processes that are running on the target using the IDE's 'system 
information' perspective. If that works, but debugging does not, then it seems like qconn cannot find the pdebug binary 
that gets started to handle debugging, but for a clean install, that is unlikely.
 
Any help ?
 
Regards
 
Dave

________________________________

From: Lakshmi Teeka [mailto:community-noreply@qnx.com]
Sent: Tue 12/29/2009 10:52 PM
To: general-ide
Subject: Debugging : Target Request Failed: Target is not responding 



Hello All,

I have QNX SDP 6.4.1 installed on Ubuntu-Linux 9.04 host machine.
I have VMWare Player  - Virtual Machine installed with  QNX 6.4.1.

I perform the following to do debugging of my application.

1. Launch my sample application as a background process in vmware target of qnx641
2. Launch the debug configuration configured for "Attach to process thro' Qconn".
3. The source path, shared library path all are set.
4. The debugger launches. But if I click the button to start debugging, getting an error
"Target Request Failed: Target is not Responding"

Can somebody point me where I am going wrong? Do I need to apply any patches?

Thanks
Lakshmi



_______________________________________________

General
http://community.qnx.com/sf/go/post44451
Attachment: Text winmail.dat 5.22 KB
Jeevan Mathew(deleted)
12/31/2009 8:15 AM
post44469
Re: RE: Debugging : Target Request Failed: Target is not responding   
Perhaps increasing the GDB MI timeout helps ?

Window -> Preferences -> C/C++ -> Debug -> GDB Mi ....
Try to double or triple it.

Jeevan
Lakshmi Teeka(deleted)
01/04/2010 8:06 AM
post44485
Re: RE: Debugging : Target Request Failed: Target is not responding   
Hello Dave/Jeevan,

Thanks for the reply.

qconn is running successfully. I am able to ping the target. 
pdebug is on the path. If i just run pdebug, it runs fine.

I have increased the timeout to 3 times too.

But what is happening is, once it gives an error for Target not responding, Time Out.

After 15-20 mins, the process is getting attached. I am copying the console msgs i get as follows:

MsgNak received - resending
Remote target is little-endian
attach 528422
[New process 528422 thread 1 (state = 0x0b)]
[New process 528422 thread 2 (state = 0x05)]
0xb033dca1 in SignalWaitinfo_r () from /opt/qnx641/target/qnx6/x86/lib/libc.so.3

After this msg, I don't see any activity going on. I get target response timeout. I click OK. After 20 mins or so, I see
 the threads getting launched. with the tinfo msgs.

Once this is successful, I am able to put breakpoints in my code, and debug my application. But this is painful.  
Waiting for 20 mins to get the process attached makes it tough to debug.

Can you please tell me, what could be the reason for such a long delay.
Is it a networking issue, or any other configuration I need to change?

My PC, has 2GB RAM, is this sufficient for qnx 641 debugging.

Thanks for your inputs.

Regards,
Lakshmi
Jeevan Mathew(deleted)
01/04/2010 8:24 AM
post44488
Re: RE: Debugging : Target Request Failed: Target is not responding   
20 minutes do remember me on arp cache problem somehow.

I do not have linux here but :

/root# uname -a
QNX Donnerstag 6.4.1 2009/05/20-17:35:56EDT x86pc x86

/root# use arp
arp [-n] hostname
arp [-nv] -a
arp [-v] -d -a
arp [-v] -d hostname [pro [iface_name]]
arp -s hostname ether_addr [temp] [pub [pro [iface_name]]]
arp -f filename


Options:
 -a             List all entries in the ARP cache.
 -d             Delete this host's ethernet from the ARP cache.
 -s             Set the ethernet address for this host in the ARP cache.
 -n             Don't try to resolve hostnames.
 -f             Load ARP cache with entries found in filename.
 -v             Be verbose.

Where:
 hostname       Host name or the IP address.
 ether_addr     Ethernet address (format 1:2:3:4:5:6).
 temp           Temporary entry, subject to time out.
 pub            Publish, answer request for this IP address.
 pathname       Pathname
 pro            Create / delete a proxy only ARP entry
 iface_name     eg: fxp0


Try to set permanent arp entry , something better ?
Jeevan
PS:
see:
http://community.qnx.com/sf/go/topc3983
and
http://community.qnx.com/sf/go/topc2233
Dave Bott(deleted)
01/04/2010 11:30 AM
post44523
RE: RE: Debugging : Target Request Failed: Target is not responding   
Another possibility is that your process is running a lot at high priority, and starving the network stack of CPU, so 
that the packets are not getting delivered.
 
What priority is your process running at, and do you expect it to run a *lot* ?
Can you 'see' the target using the 'system information' perspective, and does it update regularly ?
 
 If you are running a shell with no problem, it's not that likely, but it is possible, Jeevan may well be on to 
something on the network side - could you be having nameserver problems ?
 
Regards
 
Dave

________________________________

From: Jeevan Mathew [mailto:community-noreply@qnx.com]
Sent: Mon 1/4/2010 5:24 AM
To: general-ide
Subject: Re: RE: Debugging : Target Request Failed: Target is not responding 



20 minutes do remember me on arp cache problem somehow.

I do not have linux here but :

/root# uname -a
QNX Donnerstag 6.4.1 2009/05/20-17:35:56EDT x86pc x86

/root# use arp
arp [-n] hostname
arp [-nv] -a
arp [-v] -d -a
arp [-v] -d hostname [pro [iface_name]]
arp -s hostname ether_addr [temp] [pub [pro [iface_name]]]
arp -f filename


Options:
 -a             List all entries in the ARP cache.
 -d             Delete this host's ethernet from the ARP cache.
 -s             Set the ethernet address for this host in the ARP cache.
 -n             Don't try to resolve hostnames.
 -f             Load ARP cache with entries found in filename.
 -v             Be verbose.

Where:
 hostname       Host name or the IP address.
 ether_addr     Ethernet address (format 1:2:3:4:5:6).
 temp           Temporary entry, subject to time out.
 pub            Publish, answer request for this IP address.
 pathname       Pathname
 pro            Create / delete a proxy only ARP entry
 iface_name     eg: fxp0


Try to set permanent arp entry , something better ?
Jeevan
PS:
see:
http://community.qnx.com/sf/go/topc3983
and
http://community.qnx.com/sf/go/topc2233






_______________________________________________

General
http://community.qnx.com/sf/go/post44488
Lakshmi Teeka(deleted)
01/05/2010 8:23 AM
post44558
Re: RE: Debugging : Target Request Failed: Target is not responding   
Hello Jeevan,

I run qnx on vmware.

Do I need to set the arp entry on vmware qnx target or linux host?
I tried setting it on linux host, but it is not helping. I see the same behavior.

I have tried the debugging on the windows host too. And i see the same behaviour on my windows host.

Thanks
Lakshmi
Dave Bott(deleted)
01/05/2010 11:15 AM
post44577
RE: RE: Debugging : Target Request Failed: Target is not responding   
Hi Lakshmi,
 
QNX Neutrino 6.4.1 (and earlier versions) runs very well on Vmware - lots of people do this. It also runs on Sun's 
VirtualBox and Microsoft's  VirtualPC.
 
What version of QNX Neutrino, and what version of vmware (player, workstation, server etc.)  are you using ? Are you 
running vmware on the same physical machine where you are running the QNX host tools (Momentics) ?
 
When I install Neutrino in vmware, I do it by configuring Vmware to use 'other' and 'other 32-bit OS'.
 
Since everything except networking appears to be working, how have you got the network configured - bridged, host-only 
etc. ? Try changing it to something else, for a test. Also, things like firewalls and Norton or ZoneAlarm could maybe 
get in the way - do you have things like that enabled - if so, try disabling them temporarily.
 
When you specify the QNX target in the momentics tools, are you using an ip address or are you using a hostname and 
expecting something to resolve it  ? Ideally, I'd just use an ip address, once you know what the vmware machine has been
 assigned by dhcp... 
 
Regards
 
Dave

________________________________

From: Lakshmi Teeka [mailto:community-noreply@qnx.com]
Sent: Tue 1/5/2010 5:23 AM
To: general-ide
Subject: Re: RE: Debugging : Target Request Failed: Target is not responding 



Hello Jeevan,

I run qnx on vmware.

Do I need to set the arp entry on vmware qnx target or linux host?
I tried setting it on linux host, but it is not helping. I see the same behavior.

I have tried the debugging on the windows host too. And i see the same behaviour on my windows host.

Thanks
Lakshmi




_______________________________________________

General
http://community.qnx.com/sf/go/post44558
Attachment: Text winmail.dat 4.88 KB
Jeevan Mathew(deleted)
01/06/2010 6:29 AM
post44652
Re: RE: RE: Debugging : Target Request Failed: Target is not responding   
Lakshmi,

Puhh :-) a hard nut this is :-) .

What do you see once you telent into your qconn form your devhost and type "info"?

So:

telent ip-of-Vmwar- target 8000

You should get qconn-broker prompt there type "info" and enter..

Do you see something ?

Also provide the .log file from within you .metadata dir in your workspace on what somebody else can comment on.

J.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems