I am getting the following message on the QNX 4.25
console (i.e. /dev/con1):
vmem.c(54): 0 page release
This looks like some sort of assert() but I have no idea
where it’s coming from. Has anyone seen this before?
Better yet, can someone tell me what can cause this?
I am using shared memory and I suspect that might be the
source of the message. It would help if someone can
confirm my suspicion.
Thanks,
Steve
–
Stephen Bardsley
Foster-Miller Technologies, Inc.
Albany, NY
518-456-9919 x120
I had a similar message recently (only pmem instead of vmem) and QNX
told me that that stems from
Proc32 memory management. I had a problem in my hardware (memory) I
swapped some mem chips and the
problem disappeared. hope that helps.
Jörg
Stephen Bardsley schrieb:
Greetings,
I am getting the following message on the QNX 4.25
console (i.e. /dev/con1):
vmem.c(54): 0 page release
This looks like some sort of assert() but I have no idea
where it’s coming from. Has anyone seen this before?
Better yet, can someone tell me what can cause this?
I am using shared memory and I suspect that might be the
source of the message. It would help if someone can
confirm my suspicion.
Thanks,
Steve
–
Stephen Bardsley
Foster-Miller Technologies, Inc.
Albany, NY
518-456-9919 x120
We have seen this problem and, in our case, it is associated with
shared memory. While we have not yet had the time to track down the
details, we get this message when a task that creates and destroys a
shared memory area crashes and does not remove the memory. The next
time the task starts and attempts to create the shared memory we get
those vmem messages. Sorry I don’t have more details, but maybe it
points out an area to check.
I had a similar message recently (only pmem instead of vmem) and QNX
told me that that stems from
Proc32 memory management. I had a problem in my hardware (memory) I
swapped some mem chips and the
problem disappeared. hope that helps.
Jörg
Stephen Bardsley schrieb:
Greetings,
I am getting the following message on the QNX 4.25
console (i.e. /dev/con1):
vmem.c(54): 0 page release
This looks like some sort of assert() but I have no idea
where it’s coming from. Has anyone seen this before?
Better yet, can someone tell me what can cause this?
I am using shared memory and I suspect that might be the
source of the message. It would help if someone can
confirm my suspicion.
Thanks,
Steve
–
Stephen Bardsley
Foster-Miller Technologies, Inc.
Albany, NY
518-456-9919 x120
hi - this is interesting.
It might be desirable that QSSL publishes all those error messages. I
know
e.g. from OpenVMS of Compaq (formerly DEC) that there was a huge
documentation
of all error messages (systems and utilities) and it was very useful for
the
system administrator at least … (
Maybe QSSL compiles such a list at least for Nto (I mean QNX RTP)
Jörg Kampmann
We have seen this problem and, in our case, it is associated with
shared memory. While we have not yet had the time to track down the
details, we get this message when a task that creates and destroys a
shared memory area crashes and does not remove the memory. The next
time the task starts and attempts to create the shared memory we get
those vmem messages. Sorry I don’t have more details, but maybe it
points out an area to check.
In article <> 39E5780F.45FADBB6@ibk-consult.de> >,
=?iso-8859-1?Q?J=F6rg?= Kampmann <> joerg.kampmann@ibk-consult.de
wrote:
I had a similar message recently (only pmem instead of vmem) and QNX
told me that that stems from
Proc32 memory management. I had a problem in my hardware (memory) I
swapped some mem chips and the
problem disappeared. hope that helps.
Jörg
Stephen Bardsley schrieb:
Greetings,
I am getting the following message on the QNX 4.25
console (i.e. /dev/con1):
vmem.c(54): 0 page release
This looks like some sort of assert() but I have no idea
where it’s coming from. Has anyone seen this before?
Better yet, can someone tell me what can cause this?
I am using shared memory and I suspect that might be the
source of the message. It would help if someone can
confirm my suspicion.
Thanks,
Steve
–
Stephen Bardsley
Foster-Miller Technologies, Inc.
Albany, NY
518-456-9919 x120
Thanks for the help, that’s good information. Some day I will get
a chance to track this down. If/when I do, I’ll let you know what
I come up with. I don’t expect to get to this for a while though,
as I have other issues to resolve.
Thanks again.
Steve
–
Stephen Bardsley
Foster-Miller Technologies, Inc.
Albany, NY