Hi, Dave G,
I have ever met a strange thing before. I am not sure if it was caused
by same reason as yours. I tell you what I met, maybe it can give you
some hints.
When I set up the debug environment for the host+target before, I have
ever used a cross-over ethernet cable to link the host and the
target(BTW, my target is a P300+16MhzRAM PC104 board). I found the
download and debug speed is very slow. The system seems waiting for
something before doing the real job. But after that, I decided to
connect both my host and target to the LAN of my office by connecting
them to the switch ports, then everything is OK. It supposed to be
faster to use cross-over cable because there will be no colisions!
Then I think about maybe it was caused by the DNS setting, route setting
or maybe gateway setting of the host. I guess (just a guess) that the
host was told to look for the those servers before to do some real
jobs(even they ares not needed when you access them by IP address or you
have your host name in you local host file.). And if some of the servers
are not exist, it may wait until time out. Maybe you can double check
that all those servers are accessible(or remove some useless ones) and
try again.
BTW, how many net cards do you use in your host? Is it two? (One to
connect you to your LAN and another is connect by cross-over cable to
the target) If so, maybe you can try to do as what I am doing now.(That
is, to use only one net card on your host and use a hub/switch to
connect the target to your LAN, or if you have free port in your LAN,
just use a normal ethernet cable to connect your target to the LAN.)
Good Luck.
Best regards
Ling
Dave G. wrote:
Hi Ling,
My computer is a 1.7G Pentium4 with 512MB of RAM. My QNX box is a 700MHz
Pentium3 with 512MB of RAM. Again, Samba and Telnet work fine with the
TCP/IP communications between the two boxes and I doubt my boxes are too
slow or memory limited. I believe the debugger running on the WinXP box is
getting into some kind of timeout that it shouldn’t and it recovers 35
seconds later. BTW, I do have both boxes defined in the hosts files on both
boxes so it shouldn’t be timing out trying to do a gethostbyname or some
such thing. I have also disabled my main network card on the WinXP box
thinking that maybe that was confusing the issue.
Dave G.
“Ling Shen” <> ling@ece.concordia.ca> > wrote in message
news:> 3EE10485.8060703@ece.concordia.ca> …
Hi, Dave G,
Is it possible that your PC is too slow or maybe the RAM size is too
small? I am using a selfhosted system, the host is running QNX 6.2.1(I
guess it may use less resources than Windows host to run Momentics.).
But when I am debugging or compiling the codes(even very small ones), I
often found the system memory usage come up to 80% (of my 384MB RAM),
and CPU usage come to 100%. I think Momentics need a high standard speed
host.
Best regards
Ling
Dave G. wrote:
I have a development environment which consists of a WinXP Pro system
running the Momentics IDE and a separate QNX box running QConn. These
two
systems are connected with a 100Mb Ethernet connection with nothing else
on
the network. The WinXP system has another Ethernet network to access
the
general network and Internet. I am debugging a set of programs that has
approx. 20 threads running. Whenever I stop at a breakpoint it takes
approx. 35 seconds for the IDE to reach a point it is willing to respond
to
mouse or keyboard. This also happens when single stepping either into
or
around function calls. Basically, anytime the IDE need to switch from a
running state to a debug/suspended state it takes 35 seconds. After a
half
dozen of these transitions I end up with a much longer delay and a
dialog
box that indicates a timeout. Has anyone else experienced this problem
and
does anyone have any suggestions on how to fix it? BTW, I also run
Samba
and telnetd on the QNX box and there is no problem with network
communications between the two boxes.
Thanx for any insight,
Dave G.
\