We are having trouble using gdb through a Phindows session. I seem to recall
a posting that addressed this, and I can’t find it again.
We get an message about using /dev/ptyp1 - then when we type run we
don’t see anything any more. We look in pidin args, and see pdebug
/dev/ptyp1 –
So - what’s the proper way to set to use gdb over a Phindows session?
Thanks - Phil
“Phil Olynyk” <phil.olynyk@eti-gaming.com> wrote in message
news:953usm$stk$1@inn.qnx.com…
We are having trouble using gdb through a Phindows session. I seem to
recall
a posting that addressed this, and I can’t find it again.
We get an message about using /dev/ptyp1 - then when we type run we
don’t see anything any more. We look in pidin args, and see pdebug
/dev/ptyp1 –
Actually, it is when we type continue…then it goes away…
But if I walk over to our one-and-only NTO box, the same sequence works
flawlessly…
So - what’s the proper way to set up to use gdb over a Phindows
session?
Thanks - Phil
We tried this and it appears to be fixed in patch A
Phil Olynyk <phil.olynyk@eti-gaming.com> wrote:
We are having trouble using gdb through a Phindows session. I seem to recall
a posting that addressed this, and I can’t find it again.
We get an message about using /dev/ptyp1 - then when we type run we
don’t see anything any more. We look in pidin args, and see pdebug
/dev/ptyp1 –
So - what’s the proper way to set to use gdb over a Phindows session?
Thanks - Phil
–
cburgess@qnx.com
I’m using patch A aka QNX 6 - so is there some magic to make it work? We are
using Phindows from a WinMe box to our QNX 6 development system. That locks
up the pterm session in Phindows when we enter ‘run’ then ‘cont’ … after
directory setup etc. If we do the same thing on a pterm session right at the
QNX6 screen, it all works as one would expect. Please outline the sequence
you use to load and start a program with gdb.
Thanks - Phil Olynyk
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:954jgh$i5l$1@nntp.qnx.com…
We tried this and it appears to be fixed in patch A
Phil Olynyk <> phil.olynyk@eti-gaming.com> > wrote:
We are having trouble using gdb through a Phindows session. I seem to
recall
a posting that addressed this, and I can’t find it again.
We get an message about using /dev/ptyp1 - then when we type run we
don’t see anything any more. We look in pidin args, and see pdebug
/dev/ptyp1 –
So - what’s the proper way to set to use gdb over a Phindows
session?
Thanks - Phil
\
cburgess@qnx.com
Phil Olynyk <phil.olynyk@eti-gaming.com> wrote:
I’m using patch A aka QNX 6 - so is there some magic to make it work? We are
using Phindows from a WinMe box to our QNX 6 development system. That locks
up the pterm session in Phindows when we enter ‘run’ then ‘cont’ … after
directory setup etc. If we do the same thing on a pterm session right at the
QNX6 screen, it all works as one would expect. Please outline the sequence
you use to load and start a program with gdb.
Thanks - Phil Olynyk
All I did was
gdb ./file
run
break main
cont
When the session is locked, could you get me a pidin, pidin mem, pidin args
ls -l /dev/ptyp* and ls -l /dev/ttyp*
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:954jgh$i5l$> 1@nntp.qnx.com> …
We tried this and it appears to be fixed in patch A
Phil Olynyk <> phil.olynyk@eti-gaming.com> > wrote:
We are having trouble using gdb through a Phindows session. I seem to
recall
a posting that addressed this, and I can’t find it again.
We get an message about using /dev/ptyp1 - then when we type run we
don’t see anything any more. We look in pidin args, and see pdebug
/dev/ptyp1 –
So - what’s the proper way to set to use gdb over a Phindows
session?
Thanks - Phil
\
cburgess@qnx.com
–
cburgess@qnx.com