Has anyone got a good solution for doing remote debugging of a Neutrino
target from Windows (such as Windows 2000)?
Our situation is that we have four licenses of CodeWarrior and are
moderately happy with them. They do provide a nice, graphical debugger that
works with pdebug over Ethernet. However, I don’t get the sense that these
are going to be long-term solution for us (or perhaps anybody for that
matter). Using Windows 2000 for our hosts is important for us, as dual
booting into RTP simply disconnects our developers from many of their toosl.
So, I’m looking for solution without CodeWarrior.
I have been using qcc and make to do my compiles and that works fine. In
fact CodeWarrior seems to provide no advantage at all. However, using the
command line debugger (ntox86-gdb) is pretty ineffecient.
Here are some options:
-
Use gdbserver instead of pdebug. Thus, we could use the Insight
debugger. The one that comes with cygwin appears to be pretty nice.
Unfortunately, it can’t target QNX as is. I assume this is because pdebug
is somehow subtley different than gdbsever. Anybody know what advantage
pdebug has over gdbserver?
-
Use ddd or another wrapper around ntox86-gdb. Not a bad approach but ddd
would require an X server running on the host. I haven’t got XFree86 to run
yet and we do have exodus here, so it’s worth a shot.
-
Compile a custom version of Insight that support the QNX target and
pdebug. This would require somebody to explain what is different about
pdebug versus gdbserver.
-
Get QNX to put their targetting information in the normal GNU stuff so I
could configure it for i386-nto right after download. Would probably be
best and would make us feel like QNX is a good strategic decision for future
developments.
-
?
I’d appreciate any insights you might have. I would think somebody has
solved this problem before. But I haven’t found any reference to it.
–Todd
hitt@battelle.org
“nntp.qnx.com” <hitt@battelle.org> wrote in message
news:91qvls$ihp$2@nntp.qnx.com…
- ?
Run Phindows on your windows boxes, and use either pdb or ddd running
natively on RtP…
–Todd
hitt@battelle.org
CodeWarrior in fact use gcc to compile, so there’s no wonder you don’t
see a difference (except gcc bundled with CW is older than one which
comes with RTP). They promiced their own compiler which supposedly had
number of benefits, but since they’ve been sold (to us 
they seem to
be in permanent transition state. Last time I heard they are rushing
Linux stuff now…
In your situation the easiest solution is to install some X server right
on Windows. Exceed would do just fine, but there are free solutions as
well. All you need is X libs and DDD on targets (comes with RTP). You’ll
need to mount your source directories from WinNT to targets to simulate
source paths there. And it makes no sense to use pdebug, there is real
native gdb-4.18 on Colin’s page.
We use similar setup here for more than a year, except for Solaris
instead of WinNT.
Has anyone got a good solution for doing remote debugging of a Neutrino
target from Windows (such as Windows 2000)?
Our situation is that we have four licenses of CodeWarrior and are
moderately happy with them. They do provide a nice, graphical debugger that
works with pdebug over Ethernet. However, I don’t get the sense that these
are going to be long-term solution for us (or perhaps anybody for that
matter). Using Windows 2000 for our hosts is important for us, as dual
booting into RTP simply disconnects our developers from many of their toosl.
So, I’m looking for solution without CodeWarrior.
I have been using qcc and make to do my compiles and that works fine. In
fact CodeWarrior seems to provide no advantage at all. However, using the
command line debugger (ntox86-gdb) is pretty ineffecient.
Here are some options:
-
Use gdbserver instead of pdebug. Thus, we could use the Insight
debugger. The one that comes with cygwin appears to be pretty nice.
Unfortunately, it can’t target QNX as is. I assume this is because pdebug
is somehow subtley different than gdbsever. Anybody know what advantage
pdebug has over gdbserver?
-
Use ddd or another wrapper around ntox86-gdb. Not a bad approach but ddd
would require an X server running on the host. I haven’t got XFree86 to run
yet and we do have exodus here, so it’s worth a shot.
-
Compile a custom version of Insight that support the QNX target and
pdebug. This would require somebody to explain what is different about
pdebug versus gdbserver.
-
Get QNX to put their targetting information in the normal GNU stuff so I
could configure it for i386-nto right after download. Would probably be
best and would make us feel like QNX is a good strategic decision for future
developments.
-
?
I’d appreciate any insights you might have. I would think somebody has
solved this problem before. But I haven’t found any reference to it.
–Todd
hitt@battelle.org
nntp.qnx.com <hitt@battelle.org> wrote:
Has anyone got a good solution for doing remote debugging of a Neutrino
target from Windows (such as Windows 2000)?
- ?
I use RTP (or QNX 4, depending on what I’m working on) on the desktop
and when I need a Windows tool, for course development, I use ICA.
This means you’d have to set up an ICA server somewhere. To share
files, use NFS or CIFS. For user friendly debug under Photon there’s
pdb or ddd (runing on Xphoton). With file sharing you could still
edit using a Windows tool through ICA. Compiles of course would be
on the RTP side.