using DDD with io-net

QNX Newsgroups (Archives) qdn.public.ddk.network
1

Hi,

I’ve seen a few postings about this subject but I have not had much
success on my own.

I’m trying to debug a network driver that has a problem and crashes
io-net. Is it possible to start DDD without it trying to use io-net for
startup?

Currently I get the following error message:

_X11TransSocketOpen: socket()failed for inet
: Unable to open socket for inet

Thanks for any suggestions

Dave

2

Same case with me.I have not been able to work with DDD for io-net.However i
am able to go till i attach the io-net process into the debugger( use the
gdb window for doing that).It just freezes at this point rendering it
useless.

Sreekanth

“Dave Edwards” <dedwards180@netscape.net> wrote in message
news:3CEB964E.8000808@netscape.net…

Hi,

I’ve seen a few postings about this subject but I have not had much
success on my own.

I’m trying to debug a network driver that has a problem and crashes
io-net. Is it possible to start DDD without it trying to use io-net for
startup?

Currently I get the following error message:

_X11TransSocketOpen: socket()failed for inet
: Unable to open socket for inet

Thanks for any suggestions

Dave

3

Do not attach to io-net. By doing so, you stop the process that controls
the TCP connection between DDD (an X client) and XPhoton (the X server).

Start a second instance of io-net when you need to trace and debug your
driver.

With gdb, you would do:

$ gdb /sbin/io-net
gdb> r -d yourDriver -p tcpip
gdb>

With ddd, you would

  1. load /sbin/io-net,
  2. run (F2) with the command line option “-d yourDriver -p tcpip”,
  3. continue (F9)


    –bl


    Dave Edwards wrote:

Hi,

I’ve seen a few postings about this subject but I have not had much
success on my own.

I’m trying to debug a network driver that has a problem and crashes
io-net. Is it possible to start DDD without it trying to use io-net
for
startup?

Currently I get the following error message:

_X11TransSocketOpen: socket()failed for inet
: Unable to open socket for inet

Thanks for any suggestions

Dave

4

Hi Bernard,

Is there a null driver that will work with io-net and X? The problem
that I’m facing is that the driver I’m trying to debug has an issue and
will take out io-net when the problem occurs, this also takes out DDD!


The target board does not have another NIC installed and my driver will
not allow a second communication to the card.

It would appear to me that, as the X driver is attempting to communicate
via 127.0.0.1(0) then a null serial driver would suffice, but as yet I
have not been able to achieve this.

Any thoughts?

Dave


Bernard Leclerc wrote:

Do not attach to io-net. By doing so, you stop the process that controls
the TCP connection between DDD (an X client) and XPhoton (the X server).

Start a second instance of io-net when you need to trace and debug your
driver.

With gdb, you would do:

$ gdb /sbin/io-net
gdb> r -d yourDriver -p tcpip
gdb

With ddd, you would

  1. load /sbin/io-net,
  2. run (F2) with the command line option “-d yourDriver -p tcpip”,
  3. continue (F9)


    –bl


    Dave Edwards wrote:


    Hi,

I’ve seen a few postings about this subject but I have not had much
success on my own.

I’m trying to debug a network driver that has a problem and crashes
io-net. Is it possible to start DDD without it trying to use io-net

for

startup?

Currently I get the following error message:

_X11TransSocketOpen: socket()failed for inet
: Unable to open socket for inet

Thanks for any suggestions

Dave
\

5

If it’s only talking to localhost (127.1), you don’t need any
driver. Try starting the first instance with just the
stack, start DDD, then start the second instance with your
driver and attach to it.

io-net -ptcpip

gdb (or ddd…)

io-net -d <your_driver> -ptcpip

-seanb

Dave Edwards <dedwards180@netscape.net> wrote:
: Hi Bernard,

: Is there a null driver that will work with io-net and X? The problem
: that I’m facing is that the driver I’m trying to debug has an issue and
: will take out io-net when the problem occurs, this also takes out DDD!


: The target board does not have another NIC installed and my driver will
: not allow a second communication to the card.

: It would appear to me that, as the X driver is attempting to communicate
: via 127.0.0.1(0) then a null serial driver would suffice, but as yet I
: have not been able to achieve this.

: Any thoughts?

: Dave


: Bernard Leclerc wrote:

:> Do not attach to io-net. By doing so, you stop the process that controls
:> the TCP connection between DDD (an X client) and XPhoton (the X server).
:>
:> Start a second instance of io-net when you need to trace and debug your
:> driver.
:>
:> With gdb, you would do:
:>
:> $ gdb /sbin/io-net
:> gdb> r -d yourDriver -p tcpip
:> gdb>
:>
:> With ddd, you would
:>
:> 1) load /sbin/io-net,
:> 2) run (F2) with the command line option “-d yourDriver -p tcpip”,
:> 3) continue (F9)
:>
:>
:> --bl
:>
:>
:> Dave Edwards wrote:
:>
:>
:>>Hi,
:>>
:>>I’ve seen a few postings about this subject but I have not had much
:>>success on my own.
:>>
:>>I’m trying to debug a network driver that has a problem and crashes
:>>io-net. Is it possible to start DDD without it trying to use io-net
:>>
:> for
:>
:>>startup?
:>>
:>>Currently I get the following error message:
:>>
:>>_X11TransSocketOpen: socket()failed for inet
:>> : Unable to open socket for inet
:>>
:>>Thanks for any suggestions
:>>
:>>Dave
:>>
:>>
:>
:>

6

Sean,

I’ve just tried this:

#io-net -p tcpip
#ddd

I now get the error message:

_X11TransSocketINETConnect: Can’t connect: errno = 261
(repeated 6 times)

Error: Can’t open display: 127.1:0

Any thoughts?

Dave


Sean Boudreau wrote:

If it’s only talking to localhost (127.1), you don’t need any
driver. Try starting the first instance with just the
stack, start DDD, then start the second instance with your
driver and attach to it.

io-net -ptcpip

gdb (or ddd…)

io-net -d <your_driver> -ptcpip

-seanb

Dave Edwards <> dedwards180@netscape.net> > wrote:
: Hi Bernard,

: Is there a null driver that will work with io-net and X? The problem
: that I’m facing is that the driver I’m trying to debug has an issue and
: will take out io-net when the problem occurs, this also takes out DDD!


: The target board does not have another NIC installed and my driver will
: not allow a second communication to the card.

: It would appear to me that, as the X driver is attempting to communicate
: via 127.0.0.1(0) then a null serial driver would suffice, but as yet I
: have not been able to achieve this.

: Any thoughts?

: Dave


: Bernard Leclerc wrote:

:> Do not attach to io-net. By doing so, you stop the process that controls
:> the TCP connection between DDD (an X client) and XPhoton (the X server).
:
:> Start a second instance of io-net when you need to trace and debug your
:> driver.
:
:> With gdb, you would do:
:
:> $ gdb /sbin/io-net
:> gdb> r -d yourDriver -p tcpip
:> gdb
:
:> With ddd, you would
:
:> 1) load /sbin/io-net,
:> 2) run (F2) with the command line option “-d yourDriver -p tcpip”,
:> 3) continue (F9)
:
:
:> --bl
:
:
:> Dave Edwards wrote:
:
:
:>>Hi,
:
:>>I’ve seen a few postings about this subject but I have not had much
:>>success on my own.
:
:>>I’m trying to debug a network driver that has a problem and crashes
:>>io-net. Is it possible to start DDD without it trying to use io-net
:
:> for
:
:>>startup?
:
:>>Currently I get the following error message:
:
:>>_X11TransSocketOpen: socket()failed for inet
:>> : Unable to open socket for inet
:
:>>Thanks for any suggestions
:
:>>Dave
:
:
:
:

7

I’m no X guru, but are you running an X server locally?
If you can ping 127.1, the stack is running as expected.

-seanb

Dave Edwards <dedwards180@netscape.net> wrote:
: Sean,

: I’ve just tried this:

: #io-net -p tcpip
: #ddd

: I now get the error message:

: _X11TransSocketINETConnect: Can’t connect: errno = 261
: (repeated 6 times)

: Error: Can’t open display: 127.1:0

: Any thoughts?

: Dave


: Sean Boudreau wrote:

:> If it’s only talking to localhost (127.1), you don’t need any
:> driver. Try starting the first instance with just the
:> stack, start DDD, then start the second instance with your
:> driver and attach to it.
:>
:> # io-net -ptcpip
:> # gdb (or ddd…)
:> # io-net -d <your_driver> -ptcpip
:>
:> -seanb

8

Sean,

I’m running X locally and can ping 127.0.0.1 without any problems.

Not sure what is going on here!

Dave


Sean Boudreau wrote:

I’m no X guru, but are you running an X server locally?
If you can ping 127.1, the stack is running as expected.

-seanb

Dave Edwards <> dedwards180@netscape.net> > wrote:
: Sean,

: I’ve just tried this:

: #io-net -p tcpip
: #ddd

: I now get the error message:

: _X11TransSocketINETConnect: Can’t connect: errno = 261
: (repeated 6 times)

: Error: Can’t open display: 127.1:0

: Any thoughts?

: Dave


: Sean Boudreau wrote:

:> If it’s only talking to localhost (127.1), you don’t need any
:> driver. Try starting the first instance with just the
:> stack, start DDD, then start the second instance with your
:> driver and attach to it.
:
:> # io-net -ptcpip
:> # gdb (or ddd…)
:> # io-net -d <your_driver> -ptcpip
:
:> -seanb