Today installed Watcom 10.6 on my windows pc.
When I try to crossdebug to my qnx pc I get the message:
***** TASK NOT LOADED ***** No such file or directory
I can browse and select the correct executable over the network; same
message.
I copied the executable to my windows pc; same message.
I know it`s discussed earlier in several ng’s, but I can’t find details for
the correct setup/program options.
If someone can remeber where to find, please let me know.
Kendall, can you give me a hint?
Another question:
can I attach a running program remotely?
Friedhelm Schuetz
H.Kleinknecht & Co. GmbH
“Kendall Bennett” <KendallB@scitechsoft.com> schrieb im Newsbeitrag
news:b5sun7$eef$1@inn.qnx.com…
Friedhelm Schütz wrote:
what’s abaout cross debugging from the ms box the qnx target?
I do that all the time with Watcom 10.6 from Windows to QNX. All you
need to do is copy across the QNX runtime libraries and headers from
your QNX development machine to your Windows box, and then you can
compile QNX apps. Using the tcp.dll for NT will allow you to connect to
tcpserv under QNX.
–
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology!
Sticked around and found tcpserv must be started in the directory of the
executable.
Remains my question about debugging a running program.
“Friedhelm Schütz” <Friedhelm.Schuetz@kleinknecht.de> schrieb im Newsbeitrag
news:b6je5t$6ib$1@inn.qnx.com…
Today installed Watcom 10.6 on my windows pc.
When I try to crossdebug to my qnx pc I get the message:
***** TASK NOT LOADED ***** No such file or directory
I can browse and select the correct executable over the network; same
message.
I copied the executable to my windows pc; same message.
I know it`s discussed earlier in several ng’s, but I can’t find details
for
the correct setup/program options.
If someone can remeber where to find, please let me know.
Kendall, can you give me a hint?
Another question:
can I attach a running program remotely?
Friedhelm Schuetz
H.Kleinknecht & Co. GmbH
“Kendall Bennett” <> KendallB@scitechsoft.com> > schrieb im Newsbeitrag
news:b5sun7$eef$> 1@inn.qnx.com> …
Friedhelm Schütz wrote:
what’s abaout cross debugging from the ms box the qnx target?
I do that all the time with Watcom 10.6 from Windows to QNX. All you
need to do is copy across the QNX runtime libraries and headers from
your QNX development machine to your Windows box, and then you can
compile QNX apps. Using the tcp.dll for NT will allow you to connect to
tcpserv under QNX.
–
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology!
“Friedhelm Schuetz” <Friedhelm.Schuetz@kleinknecht.de> wrote:
Sticked around and found tcpserv must be started in the directory of the
executable.
Remains my question about debugging a running program.
I know under self-hosted you could do “wd pid” to take control of
a running process. I don’t expect that the windows native wd would
have such a command-line argument available or understood.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
David Gibbs <dagibbs@qnx.com> wrote:
“Friedhelm Schuetz” <> Friedhelm.Schuetz@kleinknecht.de> > wrote:
Sticked around and found tcpserv must be started in the directory of the
executable.
Remains my question about debugging a running program.
I know under self-hosted you could do “wd pid” to take control of
a running process. I don’t expect that the windows native wd would
have such a command-line argument available or understood.
I’m told that I’m wrong about the windows wd, but that in fact,
“Processing of the debugee ‘name’ is done by the target side
trap file (std.trp), not the host side debugger.”
So, you might be ok.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Yes it works.
Tried that morning; runs like a charm. wd looks like qnx, wdw works also.
Watcom did a good job.
Friedhelm Schuetz
H.Kleinknecht & Co. GmbH
“David Gibbs” <dagibbs@qnx.com> schrieb im Newsbeitrag
news:b6kc0j$m7$3@nntp.qnx.com…
David Gibbs <> dagibbs@qnx.com> > wrote:
“Friedhelm Schuetz” <> Friedhelm.Schuetz@kleinknecht.de> > wrote:
Sticked around and found tcpserv must be started in the directory of
the
executable.
Remains my question about debugging a running program.
I know under self-hosted you could do “wd pid” to take control of
a running process. I don’t expect that the windows native wd would
have such a command-line argument available or understood.
I’m told that I’m wrong about the windows wd, but that in fact,
“Processing of the debugee ‘name’ is done by the target side
trap file (std.trp), not the host side debugger.”
So, you might be ok.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
“Rick Lake” <rwlake@spamfree.domain.invalid> wrote in message
news:b2gr39$s2u$1@inn.qnx.com…
OK, there’s a third option: push QNX6. But unfortunately our management
has dropped QNX in favor of Solaris and/or Linux, and is slowly fasing out
the 160+ QNX OS licenses we bought.
Just curious, what was your management’s justification for the switch? That
has to be an expensive (and risky) proposition. QSSL needs to understand
why they lost so that they can address the problem.
Regards,
Steve
Steve Cobb <steve_cobb0@yahoo.com> wrote:
“Rick Lake” <> rwlake@spamfree.domain.invalid> > wrote in message
news:b2gr39$s2u$> 1@inn.qnx.com> …
OK, there’s a third option: push QNX6. But unfortunately our management
has dropped QNX in favor of Solaris and/or Linux, and is slowly fasing out
the 160+ QNX OS licenses we bought.
Just curious, what was your management’s justification for the switch? That
has to be an expensive (and risky) proposition. QSSL needs to understand
why they lost so that they can address the problem.
Same old story: lack of support of standard applications. QNX’s core
business is in the realtime market and can’t compete (yet) in the
general-purpose OS market. Does Oracle run under QNX? Even if it does, the
support would be minimal and you need special IT-employees. All of this
means too much business risk. Management always tend to follow the general
trends and don’t want to be dependent on rare specialists that can “hold
the company hostage”, so to speak.
Regards,
Steve