Hi,
I have this weird problem…
We are using QNX4.23.
I’m using UDP socket to send/receive a quite amount of data at 500HZ.
The program itself works fine.
However, if I run it for a long time(I don’t know how long should it
be), I can’t compile any program any more before I reboot the machine.
When I run the program for a short time, then it looks fine.
I don’t have any idea how this UDP connection is connected to compiling.
Any other program/network is fine except the compiling.
I can even re-run the program and it works just fine.
Any body had a similar problem before?
Any suggestion could be very helpful.
Thanks,
-Jaeheung
“Jaeheung Park” <park73@stanford.edu> wrote in message
news:big957$imt$1@inn.qnx.com…
Hi,
I have this weird problem…
We are using QNX4.23.
I’m using UDP socket to send/receive a quite amount of data at 500HZ.
The program itself works fine.
However, if I run it for a long time(I don’t know how long should it
be), I can’t compile any program any more before I reboot the machine.
When I run the program for a short time, then it looks fine.
I don’t have any idea how this UDP connection is connected to compiling.
Any other program/network is fine except the compiling.
I can even re-run the program and it works just fine.
Any body had a similar problem before?
Any suggestion could be very helpful.
Could you expand a little bit on “doesn’t compile”.?
Thanks,
-Jaeheung
It starts compiling and it is just stuck.
If I do “cc … file.cpp”, then it is not progessing any more.
I have to use Ctrl-c to stop it.
-Jaeheung
Mario Charest wrote:
“Jaeheung Park” <> park73@stanford.edu> > wrote in message
news:big957$imt$> 1@inn.qnx.com> …
Hi,
I have this weird problem…
We are using QNX4.23.
I’m using UDP socket to send/receive a quite amount of data at 500HZ.
The program itself works fine.
However, if I run it for a long time(I don’t know how long should it
be), I can’t compile any program any more before I reboot the machine.
When I run the program for a short time, then it looks fine.
I don’t have any idea how this UDP connection is connected to compiling.
Any other program/network is fine except the compiling.
I can even re-run the program and it works just fine.
Any body had a similar problem before?
Any suggestion could be very helpful.
Could you expand a little bit on “doesn’t compile”.?
Thanks,
-Jaeheung
\
Jaeheung Park <park73@stanford.edu> wrote:
I’m using UDP socket to send/receive a quite amount of data at 500HZ.
The program itself works fine.
However, if I run it for a long time(I don’t know how long should it
be), I can’t compile any program any more before I reboot the machine.
When I run the program for a short time, then it looks fine.
I don’t have any idea how this UDP connection is connected to compiling.
Any other program/network is fine except the compiling.
I can even re-run the program and it works just fine.
Is your UDP application leaking memory or other resources? (compiling
and linking can require large amounts of memory). Use something like
“sin” (sin mem, sin fd, sin in) to monitor this. Is it running ready
at a low priority (since compiling will drop itself to 9o, it will appear
to hang if something else is running ready)? - check with “sin”.
John Garvey wrote:
Jaeheung Park <> park73@stanford.edu> > wrote:
I’m using UDP socket to send/receive a quite amount of data at 500HZ.
The program itself works fine.
However, if I run it for a long time(I don’t know how long should it
be), I can’t compile any program any more before I reboot the machine.
When I run the program for a short time, then it looks fine.
I don’t have any idea how this UDP connection is connected to compiling.
Any other program/network is fine except the compiling.
I can even re-run the program and it works just fine.
Is your UDP application leaking memory or other resources? (compiling
and linking can require large amounts of memory). Use something like
“sin” (sin mem, sin fd, sin in) to monitor this. Is it running ready
at a low priority (since compiling will drop itself to 9o, it will appear
to hang if something else is running ready)? - check with “sin”.
Thanks for the reply.
However, I don’t know what to look at it with “sin”
The followings are the result when I did “sin mem, sin fd, sin in”.
Can you see something there?
-Jaeheung
$ sin mem
PROGRAM PID
sys/Proc32 1
0005 F0000000 110592 -B-3--------DC- 000D F0040000 268M
-B-3--------D–
10A9 0033000 28672 -B–±-G-----C- 0009 FF801000 29056
—3—G-------
0011 FF800000 2048 -------G------- 0049 3F70000 4096
-B-----G-------
0081 3F74000 167936 -B-----G------- 00C9 3F71000 12288
-B-----G-------
sys/Slib32 2
0005 0026000 49152 -BS3---------C- 000D 0032000 4096
-B-3-----------
10A1 0026000 49152 -BS3±-G-----C-
/bin/Fsys 4
0005 23BA000 73728 -B-3--------DC- 000D 23BA000 9687k
-BS3-----------
0015 354C000 10174k -BS3±--------- 001D 0053000 57344
-BS3±-------C-
0025 3F18000 20480 -BS3±--------- 002D 23BA000 9797k
-BS3±---------
0035 3F1D000 16384 -BS3±-------C- 003D 23BA000 9797k
-BS3±---------
/bin/Fsys.eide 5
0005 0053000 57344 -BS3---------C- 000D 354C000 10174k
-BS3-----------
0015 40F0000 8192 -B-3-------MD-- 001D 40B0000 65536
-B-3-------MD–
0025 40A0000 65536 -B-3-------MD-- 002D 23BA000 9797k
-BS3±---------
idle 8
10E1 3506000 40960 -B-3—G—M—
//1/bin/Dev32 17
0005 40C7000 32768 -BS3---------C- 000D 3F27000 94208
-BS3-----------
0015 40C2000 20480 -BS3±--------- 001D 3F65000 40960
-BS3±-------C-
0025 40C2000 20480 -BS3±--------- 002D 3F65000 40960
-BS3±-------C-
0035 3F21000 16384 -BS3±--------- 003D 3F61000 16384
-BS3±-----M—
0045 40C1000 4096 -BS3±-----M— 004D 3F50000 12288
-BS3±-------C-
0055 3F21000 16384 -BS3±--------- 005D 3F50000 12288
-BS3±-------C-
0065 409E000 8192 -BS3-------M— 006D 3F53000 8192
-BS3-------M—
//1/bin/Dev32.ansi 20
0005 3F65000 40960 -BS3---------C- 000D 40C2000 20480
-BS3-----------
0015 00A0000 65536 -----------MD-- 001D 3F27000 94208
-BS3±---------
0025 40C7000 32768 -BS3±-------C- 002D 3F27000 94208
-BS3±---------
0035 40C7000 32768 -BS3±-------C- 003D 3F61000 16384
-BS3-------M—
0045 40C1000 4096 -BS3-------M— 004D 3F55000 49152
-B-3-------M—
//1/bin/Dev32.pty 24
0005 3F50000 12288 -BS3---------C- 000D 3F21000 16384
-BS3-----------
0015 3F27000 94208 -BS3±--------- 001D 40C7000 32768
-BS3±-------C-
0025 3F27000 94208 -BS3±--------- 002D 40C7000 32768
-BS3±-------C-
0065 409E000 8192 -BS3±-----M— 006D 3F53000 8192
-BS3±-----M—
//1/bin/Iso9660fsys 25
0005 3526000 28672 -B-3--------DC- 000D 3526000 61440
-B-3-----------
//1/bin/Fsys.floppy 27
0005 3F1D000 16384 -BS3---------C- 000D 3F18000 20480
-BS3-----------
003D 23BA000 9797k -BS3±---------
10D9 3F13000 20480 -B-3—G-±MD–
//1/bin/Pipe 28
0005 34B7000 16384 -B-3--------DC- 000D 34B7000 32768
-B-3-----------
//1/bin/Net 33
0005 351E000 32768 -B-3---------C- 000D 34FE000 32768
-B-3-----------
0015 3F0A000 36864 -BS3±-------C- 001D 34D9000 102400
-BS3±---------
//1/bin/Net.ether82557 35
0005 3F0A000 36864 -BS3---------C- 000D 34D9000 102400
-BS3-----------
0015 3F25000 8192 -B-3-+±—MD-- 001D 34F2000 49152
-B-3-+±—MD–
0025 40C0000 4096 -B-3-+±—MD-- 002D 409D000 4096
-B-3-+±—MD–
//1//usr/ucb/Socket 42
0005 451D000 208896 -B-3--------DC- 000D 451D000 466944
-B-3-----------
//1//usr/bin/syslogd 50
0007 3457000 32768 -B-3--------DC- 000F 3457000 32768
-B-3-----------
//1//usr/ucb/inetd 52
0007 349D000 40960 -B-3--------DC- 000F 349D000 24576
-B-3-----------
//1/bin/tinit 57
0007 34C5000 16384 -B-3--------DC- 000F 34C5000 28672
-B-3-----------
//1/bin/login 58
0007 3476000 24576 -B-3--------DC- 000F 3476000 20480
-B-3-----------
//1//usr/ucb/telnetd 59
0007 343F000 53248 -B-3--------DC- 000F 343F000 36864
-B-3-----------
//1/bin/ksh 62
0007 331F000 69632 -B-3--------DC- 000F 331F000 45056
-B-3-----------
//1/bin/sin 445
0007 63BD000 36864 -B-3--------DC- 000F 63BD000 40960
-B-3-----------
$ sin fd
PROGRAM PID
sys/Proc32 1
sys/Slib32 2
/bin/Fsys 4
/bin/Fsys.eide 5
idle 8
//1/bin/Dev32 17
//1/bin/Dev32.ansi 20
//1/bin/Dev32.pty 24
//1/bin/Iso9660fsys 25
5 - //1/dev/cd0
//1/bin/Fsys.floppy 27
//1/bin/Pipe 28
//1/bin/Net 33
//1/bin/Net.ether82557 35
//1//usr/ucb/Socket 42
//1//usr/bin/syslogd 50
0 - //1/dev/null 1 - //1/dev/null
2 - //1/dev/null 3 - //1 [@9cb90]
5 - //1/tmp/syslog
//1//usr/ucb/inetd 52
0 - //1/dev/null 1 - //1/dev/null
2 - //1/dev/null 4 - //1 [@9c990]
5 - //1 [@9c890] 6 - //1 [@9c790]
7 - //1 [@9c690] 8 - //1 [@9c590]
9 - //1 [@9c510] 10 - //1 [@9c410]
11 - //1 [@9c310] 12 - //1 [@9c210]
//1/bin/tinit 57
//1/bin/login 58
0 - //1/dev/con1 1 - //1/dev/con1
2 - //1/dev/con1
//1//usr/ucb/telnetd 59
0 - //1 [@9a590] 1 - //1 [@9a590]
2 - //1 [@9a590] 3C- //1/dev/ptyp0
4 - //1/dev/ttyp0
//1/bin/ksh 62
0 - //1/dev/ttyp0 1 - //1/dev/ttyp0
2 - //1/dev/ttyp0 4 - //1/dev/ttyp0
10C- //1/dev/ttyp0
//1/bin/sin 447
0 - //1/dev/ttyp0 1 - //1/dev/ttyp0
2 - //1/dev/ttyp0 4 - //1/dev/ttyp0
$ sin in
Node CPU Machine Speed Memory Ticksize Display
Flags
1 686/687 PCI 34025 55111k/67756k 2.0ms VGA Color
-3P±---------8P
Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
89k 155k 23120 0 64 100 64 500 125 1 76M/
113M
Boot from Hard at Aug 27 10:56 Locators:
Jaeheung Park <park73@stanford.edu> wrote:
However, I don’t know what to look at it with “sin”
The followings are the result when I did “sin mem, sin fd, sin in”.
Can you see something there?
Where is your UDP program, I don’t see it running?! You should start
it, leave it running, and then monitor with the various “sin” usages
to track whether it is leaking any resource or priority issues.
$ sin in
Node CPU Machine Speed Memory Ticksize Display
Flags
1 686/687 PCI 34025 55111k/67756k 2.0ms VGA Color
^^^^^^^^^^^^^
For example, whilst your application is running, does this value
decrease? Similarly, in “sin fd” is it acquiring file descriptors?
In “sin mem”, is the size of its data segment growing. Etcetera …
I checked it…
When I run the program, the memory drops a little bit and stays there.
The memory comes back to the same point when I quit the program.
-Jaeheung
John Garvey wrote:
Jaeheung Park <> park73@stanford.edu> > wrote:
However, I don’t know what to look at it with “sin”
The followings are the result when I did “sin mem, sin fd, sin in”.
Can you see something there?
Where is your UDP program, I don’t see it running?! You should start
it, leave it running, and then monitor with the various “sin” usages
to track whether it is leaking any resource or priority issues.
$ sin in
Node CPU Machine Speed Memory Ticksize Display
Flags
1 686/687 PCI 34025 55111k/67756k 2.0ms VGA Color
^^^^^^^^^^^^^
For example, whilst your application is running, does this value
decrease? Similarly, in “sin fd” is it acquiring file descriptors?
In “sin mem”, is the size of its data segment growing. Etcetera …
“Jaeheung Park” <park73@stanford.edu> wrote in message
news:bign3a$sl4$1@inn.qnx.com…
I checked it…
When I run the program, the memory drops a little bit and stays there.
The memory comes back to the same point when I quit the program.
Get sysmon at ftp://ftp.qnx.com/usr/free/qnx4/os/utils/misc/sysmon.tgz.
This utility will show you what process is using the CPU. I would guess a
program of higher priority then the compiler is using all the CPU. Sysmon
will tell you which program is using the CPU. The compiler is setup to
lower its priority (feature of the OS) so it probably drop from the default
priority 10 to priority 9. Any process using 100 % CPU at priority 10 will
prevent compiler from running.
-Jaeheung
John Garvey wrote:
Jaeheung Park <> park73@stanford.edu> > wrote:
However, I don’t know what to look at it with “sin”
The followings are the result when I did “sin mem, sin fd, sin in”.
Can you see something there?
Where is your UDP program, I don’t see it running?! You should start
it, leave it running, and then monitor with the various “sin” usages
to track whether it is leaking any resource or priority issues.
$ sin in
Node CPU Machine Speed Memory Ticksize Display
Flags
1 686/687 PCI 34025 55111k/67756k 2.0ms VGA Color
^^^^^^^^^^^^^
For example, whilst your application is running, does this value
decrease? Similarly, in “sin fd” is it acquiring file descriptors?
In “sin mem”, is the size of its data segment growing. Etcetera …
Jaeheung Park <park73@stanford.edu> wrote:
JP > Thanks for the reply.
JP > However, I don’t know what to look at it with “sin”
JP > The followings are the result when I did “sin mem, sin fd, sin in”.
JP > Can you see something there?
JP > -Jaeheung
JP > $ sin in
JP > Node CPU Machine Speed Memory Ticksize Display
JP > Flags
JP > 1 686/687 PCI 34025 55111k/67756k 2.0ms VGA Color
JP > -3P±---------8P
JP > Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
JP > 89k 155k 23120 0 64 100 64 500 125 1 76M/
JP > 113M
JP > Boot from Hard at Aug 27 10:56 Locators:
This is just a shot in the dark. But I don’t see any nameloc’s running.
I see that this is node 1 on a 1 node network, but you still need nameloc
to run a licensed product.
–
Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net