Can't run Watcom debugger through Phindows

Hi,

I can’t invoke the Watcom debugger (either wvideo for Watcom 9.52 or
wd for Watcom 10.6) through Phindows. When I try it, I get the following
error message:
qnxterm – unknown qnx terminal environment
unable to open debugger console
eventhough the pterm I invoke the command from is set to qnxm.

Here’s some info on the situation:

  • connected to a QNX node through Phindows on a LAN; compiling
    and debugging code on that QNX node
  • software versions:
    QNX 4.24
    Watcom C 9.52 & 10.6
    Photon 1.12
    Phindows 1.20
    Windows NT Workstation 4.0, Service Pack 5

Has anyone run into this problem before? Any suggestions/workarounds
would be much appreciated.

Thanks.

Eugene Wang
Eugene_Wang@Mitel.Com

Try to increase the number of normal console Dev.con. just use “Dev.con -n9”
and take care does tinit does not use all these.
check the command
“tinit -T /dev/con1 -t /dev/con*”

\

Bye Sascha( sascha@bitctrl.de )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: sascha@bitctrl.de
WWW: http://www.bitctrl.de


Eugene Wang <Eugene_Wang@Mitel.Com> schrieb in im Newsbeitrag:
9b2vu8$nog$1@inn.qnx.com

Hi,

I can’t invoke the Watcom debugger (either wvideo for Watcom 9.52 or
wd for Watcom 10.6) through Phindows. When I try it, I get the following
error message:
qnxterm – unknown qnx terminal environment
unable to open debugger console
eventhough the pterm I invoke the command from is set to qnxm.

Here’s some info on the situation:

  • connected to a QNX node through Phindows on a LAN; compiling
    and debugging code on that QNX node
  • software versions:
    QNX 4.24
    Watcom C 9.52 & 10.6
    Photon 1.12
    Phindows 1.20
    Windows NT Workstation 4.0, Service Pack 5

Has anyone run into this problem before? Any suggestions/workarounds
would be much appreciated.

Thanks.

Eugene Wang
Eugene_Wang@Mitel.Com

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 &

I tried “Dev.con -n16 &” also but got the same error.

Eugene Wang
Eugene_Wang@Mitel.Com


“Sascha Morgenstern” <sascha@bitctrl.de> wrote in message
news:9b3auh$t8n$1@inn.qnx.com

Try to increase the number of normal console Dev.con. just use
“Dev.con -n9”
and take care does tinit does not use all these.
check the command
“tinit -T /dev/con1 -t /dev/con*”

\

Bye Sascha( > sascha@bitctrl.de > )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: > sascha@bitctrl.de
WWW: > http://www.bitctrl.de


Eugene Wang <> Eugene_Wang@Mitel.Com> > schrieb in im Newsbeitrag:
9b2vu8$nog$> 1@inn.qnx.com> …
Hi,

I can’t invoke the Watcom debugger (either wvideo for Watcom 9.52 or
wd for Watcom 10.6) through Phindows. When I try it, I get the
following
error message:
qnxterm – unknown qnx terminal environment
unable to open debugger console
eventhough the pterm I invoke the command from is set to qnxm.

Here’s some info on the situation:

  • connected to a QNX node through Phindows on a LAN; compiling
    and debugging code on that QNX node
  • software versions:
    QNX 4.24
    Watcom C 9.52 & 10.6
    Photon 1.12
    Phindows 1.20
    Windows NT Workstation 4.0, Service Pack 5

Has anyone run into this problem before? Any suggestions/workarounds
would be much appreciated.

Thanks.

Eugene Wang
Eugene_Wang@Mitel.Com

\

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.

How about:
tinit -T /dev/con1 -t /dev/con[2-8] &

“Alex” <acellarius@systems104.co.za> 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.

How about:
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
Phindows. :frowning:

  • Eugene

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”?
You said that many people working on the machine.
Are there running “wd”, if yes how many running?

try sin fd | grep con. Are there all possible cons used.

\

Bye Sascha( sascha@bitctrl.de )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: sascha@bitctrl.de
WWW: http://www.bitctrl.de


Eugene Wang <Eugene_Wang@Mitel.Com> schrieb in im Newsbeitrag:
9bkotp$fhm$1@inn.qnx.com

“Alex” <> acellarius@systems104.co.za> > 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.

How about:
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
Phindows. > :frowning:

  • Eugene

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 use
(-c=… option).

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”?
You said that many people working on the machine.
Are there running “wd”, if yes how many running?

try sin fd | grep con. Are there all possible cons used.


Bye Sascha( > sascha@bitctrl.de > )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: > sascha@bitctrl.de
WWW: > http://www.bitctrl.de

Eugene Wang <> Eugene_Wang@Mitel.Com> > schrieb in im Newsbeitrag:
9bkotp$fhm$> 1@inn.qnx.com> …

“Alex” <> acellarius@systems104.co.za> > 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.

How about:
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
Phindows. > :frowning:

  • Eugene

“Dean Douthat” <ddouthat@faac.com> wrote in message
news:3ADEE24D.9B4EC868@faac.com

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
use
(-c=… option).

Oh wow, that was interesting! I tried that, and saw the wd console start
up,
though the borders of the console were garbled – with text characters
instead
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.


Bye Sascha( > sascha@bitctrl.de > )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: > sascha@bitctrl.de
WWW: > http://www.bitctrl.de

Eugene Wang <> Eugene_Wang@Mitel.Com> > schrieb in im Newsbeitrag:
9bkotp$fhm$> 1@inn.qnx.com> …

“Alex” <> acellarius@systems104.co.za> > 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.

How about:
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
Phindows. > :frowning:

  • Eugene
    \

upgrade phindows to 1.2 or set your pterm to the other type - you will only get
integer divide by zero with the old 1.0 version and either ansi or qnx term type
(I forget which).

I have run the debugger in phindows no problems.

The garbled text characters will also disappear and be replaced with lines, etc,
when you switch to the other term type (ANSI I think!)

Eugene Wang wrote:

“Dean Douthat” <> ddouthat@faac.com> > wrote in message
news:> 3ADEE24D.9B4EC868@faac.com> …
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
use
(-c=… option).

Oh wow, that was interesting! I tried that, and saw the wd console start
up,
though the borders of the console were garbled – with text characters
instead
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.

\

Bye Sascha( > sascha@bitctrl.de > )

Sascha Morgenstern
BitCtrl Systems GmbH
Weißenfelser Straße 67
Germany - 04229 Leipzig
Phon. +49 341 490 670
FAX. +49 341 490 67 15
eMail: > sascha@bitctrl.de
WWW: > http://www.bitctrl.de

Eugene Wang <> Eugene_Wang@Mitel.Com> > schrieb in im Newsbeitrag:
9bkotp$fhm$> 1@inn.qnx.com> …

“Alex” <> acellarius@systems104.co.za> > 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.

How about:
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
Phindows. > :frowning:

  • Eugene

    \

Lance Roberts
Analyst Programmer
email: lance@econz.co.nz web: http://www.econz.co.nz
Ph: +64 9 361 1947 Fax: +64 9 378 9010
ECONZ (1971) Ltd. mail: PO Box 68-261, Newton, Auckland, New Zealand.