This is my error message:
/bin/nameloc terminated (SIGSEGV) at 0007:00023799
Traceinfo output:
aug 01 15:11:32 1 00001013 Run fault 35 000B 000D file://1/bin/nameloc
(x013 is "Run fault %d %04.4x %04.4x %s ")
How should we understand that message:
-The nameloc process SIGSEGV to the operating system?
or
-Another process SIGSEGV to the nameloc process segment?
One day before, we had Socklet terminated (SIGSEGV) at …
Someone could help me?
“Jean-Jacques Levesque (mobile)” <jlevesque@sigma-techno.com> wrote:
This is my error message:
/bin/nameloc terminated (SIGSEGV) at 0007:00023799Traceinfo output:
aug 01 15:11:32 1 00001013 Run fault 35 000B 000D file://1/bin/nameloc
(x013 is "Run fault %d %04.4x %04.4x %s ")
This should be followed by a second line that says something like
“Last run fault at…” and contains some more information, including
the address at which it faulted. If you didn’t see the error message,
you should make sure to grab both traceinfo entries.
How should we understand that message:
-The nameloc process SIGSEGV to the operating system?
or
The nameloc process died do to a segmentation violation (generally
a bad pointer reference).
One day before, we had Socklet terminated (SIGSEGV) at …
Someone could help me?
When posting questions/issues like this, please post version information
as well. The output of “sin ver” while Socklet is running, and the output
of “which -lf nameloc” will at least tell people what versions of
executables are running.
-David
Do you happen to have a lot of processes registering Global names (start
with ‘/’, check with “sin names”) across your network?
I saw similar when I had 200+ processes registering their names, but only
the system they ran on had Proc32 set for this many names, the other
system’s with lower Proc32 settings would have nameloc die (1 of pair of
nameloc processes). nameloc & Proc32 from Dec99 CD
-Paul
Jean-Jacques Levesque (mobile) <jlevesque@sigma-techno.com> wrote in message
news:tDUh5.23451$NS6.367145@news.globetrotter.net…
This is my error message:
/bin/nameloc terminated (SIGSEGV) at 0007:00023799Traceinfo output:
aug 01 15:11:32 1 00001013 Run fault 35 000B 000D file://1/bin/nameloc
(x013 is "Run fault %d %04.4x %04.4x %s ")
How should we understand that message:
-The nameloc process SIGSEGV to the operating system?
or
-Another process SIGSEGV to the nameloc process segment?One day before, we had Socklet terminated (SIGSEGV) at …
Someone could help me?
Hum if you said you had Socket and nameloc crash,
my first guess would be a hardware problem (bad memory).
“Jean-Jacques Levesque (mobile)” <jlevesque@sigma-techno.com> wrote in
message news:tDUh5.23451$NS6.367145@news.globetrotter.net…
This is my error message:
/bin/nameloc terminated (SIGSEGV) at 0007:00023799Traceinfo output:
aug 01 15:11:32 1 00001013 Run fault 35 000B 000D file://1/bin/nameloc
(x013 is "Run fault %d %04.4x %04.4x %s ")
How should we understand that message:
-The nameloc process SIGSEGV to the operating system?
or
-Another process SIGSEGV to the nameloc process segment?One day before, we had Socklet terminated (SIGSEGV) at …
Someone could help me?