“Dean Douthat” <email@example.com> wrote in message
Are you running wd via Photon pterm? If so, we have noticed that wd can’t
seem to find pseudo-teletypes beyone the first group of 16 (p). To work
around this, try specifying the pseudo-teletype of your pterm for wd to
Oh wow, that was interesting! I tried that, and saw the wd console start
though the borders of the console were garbled – with text characters
of lines… then Phindows dies with an “integer divide by zero” error!
Here’s more info on the system: I guess many people are connecting to
the QNX server through Phindows and launching pterm sessions so the
server has been setup to run the following Dev.pty’s:
Dev.pty -n16 -lp -I1024 -O1024 &
Dev.pty -n16 -lq -I1024 -O1024 &
Dev.pty -n16 -lr -I1024 -O1024 &
Dev.pty -n16 -ls -I1024 -O1024 &
Dev.pty -n16 -lt -I1024 -O1024 &
Dev.pty -n16 -lu -I1024 -O1024 &
Sascha Morgenstern wrote:
On our qnxserver we run Dev.con with -n8 (9 should be working to) and
Dev.pty with -n16.
Tinit is called with tinit -t /dev/con[2-4] -T /dev/con1
And it worked, I just tried it.
What does it say if you start “wd”?
I get the following two lines:
qnxterm – unknown qnx terminal environment
unable to open debugger console
You said that many people working on the machine.
Are there running “wd”, if yes how many running?
No other wd sessions are running. The way things are setup here,
there are 4 QNX servers (nodes 1 to 4). Each of the servers has
a particular function: node 1 for code repository, node 2 for release
builds etc. All the developers have Windows NT machines at their
desks and connect to QNX node 4 (where their accounts are located)
through Phindows, to do development work.
The problem with wd failing when invoked from a pterm within
Phindows has been a known problem here for years; everybody
just seems to take it for granted and found ways to work around
it, like debugging at the server console or on a standalone machine
in the lab. I just started working here a while ago and though this
was a major PITA so am trying to track down a fix for it.
try sin fd | grep con. Are there all possible cons used.
1 to 8 are used, 9 & 10 are free.
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: > firstname.lastname@example.org
WWW: > http://www.bitctrl.de
Eugene Wang <> Eugene_Wang@Mitel.Com> > schrieb in im Newsbeitrag:
9bkotp$fhm$> email@example.com> …
“Alex” <> firstname.lastname@example.org> > wrote in message
news:> 3AD62D4B.C22845A@systems104.co.za> …
Eugene Wang wrote:
Thanks for the suggestion Sascha, but I’m afraid it didn’t work.
The node had these settings to begin with:
Dev.con -n10 &
tinit -T/dev/con[1-8] -tcon[1-8] TERM=qnx &
This tinit line looks a little odd.
tinit -T /dev/con1 -t /dev/con[2-8] &
This QNX server is used by many people so I wasn’t able to try out
your suggestion until today. I took out the “TERM=qnx” from the
tinit line in the sysinit. file, rebooted the machine… and got
the same error when I tried to launch the Watcom debugger in