John Bowen <John.Bowen@grc.nasa.gov> wrote:
“Graeme Peterson” <> firstname.lastname@example.org> > wrote in message
news:93ksnt$lqt$> email@example.com> …
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
John Bowen wrote:
I’m sure this is a terminal device configuration problem, but I don’t
how to fix it. When I run my program using ddd, I get an error in the
pane indicating the following:
Starting program: /home/…
fork() failed: Invalid argument
pty: Invalid argument.
Yes … my first idea is to look into the SOURCES
of ddd. ddd is part of the QNX RTP distribution
and must be distributed under the GPL, that means
they must be available for everyone.
So … WHERE are the SOURCES!!
Ouch. Did I strike a nerve here?
As far as I understand (and I am not a lawyer), the sources
have to be available, and anyone who asks will receive them.
The source to the gnu binutils, compiler and gdb are found at:
‘ddd’ was configured and compiled stock. We made no special
changes. You can find it at:
This error is coming from one of our files in gdb:
gdb/ser-qnxpty.c: printf_unfiltered(“fork() failed: %s\n”,
We are trying to fork gdb, and then exec pdebug so we can talk to it.
I don’t think fork() should be returning EINVAL… Are you running out
It looks like we have a winner! No More RAM. The fork() should
probably be returning ENOMEM, as opposed to EINVAL, though. My RTP
development machine has 33 Meg used with only a pterm open (so I can
run ‘pidin in’). Perhaps you should consider getting a bigger, faster,
RAM filled development machine to target your pc/104, then you can do
remote debugging by running pdebug on the pc/104, and ddd/gdb on the
development machine. TCP or serial connections will work. The other
option is to slay off things you don’t need, like fontsleuth, saver, or
any other managers/drivers you are not using.
A monster development box seems safer, though.
That is very possible, but I don’t understand why it should. I have an
embedded 486 PC/104 with 32MB of RAM on it. Even when I’m not running ddd
the memory usage bar is almost pegged. What is hogging it? How can I get
more usable memory?
Please exit Photon to a text console, and try gdb. Let me know how that
QNX Tools Group
QNX Tools Group