QNX Neutrino Programmer's Guide [6.5.0 SP1] - QNX Software ...

© 2012, QNX Software Systems Limited Debugging
TCP/IP
Port
1234
inetd
Port
1234
Port
1234
pdebug pdebug pdebug
For a TCP/IP dynamic port connection, the inetd process will manage the port.
Note that this method is also suitable for one or more developers. It’s effectively what
the qconn daemon does to provide support to remote IDE components; qconn listens
to a port and spawns pdebug on a new, dynamically determined port.
Sample buildfile for dynamic port sessions
The following buildfile supports multiple sessions specifying the same port. Although
the port for each session on the pdebug side is the same, inetd causes unique ports
to be used on the debugger side. This ensures a unique socket pair for each session.
Note that inetd should be included and started in your boot image. The pdebug
program should also be in your boot image (or available from a mounted filesystem).
The config files could be built into your boot image (as in this sample buildfile) or
linked in from a remote filesystem using the [type=link] command:
[type=link] /etc/services=/mount_point/services
[type=link] /etc/inetd.conf=/mount_point/inetd.conf
Here’s the buildfile:
[virtual=x86,bios +compress] boot = {
startup-bios -N node428
PATH=/proc/boot:/bin:/apk/bin_nto:./ procnto
}
[+script] startup-script = {
# explicitly running in edited mode for the console link
devc-ser8250 -e -b115200 &
reopen
display_msg Welcome to Neutrino on a PC-compatible BIOS system
# tcp/ip with a NE2000 Ethernet adaptor
June 14, 2012 Chapter 1 • Compiling and Debugging 27