program keeps on failing - SIGSEGV.

[Gino Castoldi_2]

Hi,

I have a copy of a program from HP called snapbdf (it lists all VxFS snapshots on a system).
The program runs fine on our
L2000 HP-UX 11.0 (64bit OS).
(L2000 has 2GB RAM).

When I run the same program on our D250 (32bit OS)(1.2GB of RAM) it fails.

I upped the value of maxssiz to it's maximum - 383MB and it still fails with these errors.

"Pid 2516 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
Memory fault(coredump)"

Any ideas on what to do?

10 points to any good answer.
Thank you
Gino

[Stefan Farrelly · Accepted solution]

I presume its a binary and not a script ? if so then you can try enabling more memory regions;

chatr +q3p enable snapbdf

and if it still falls over enable the 4th region;

chatr +q4p enable snapbdf

and try that. Sounds to me like its not designed to run on 32bit OS as its running away and expanding so large. I cant imagine it actually needs in excess of 393MB to run!

[John Poff]

Hi Gino,

Is your snapbdf program a 64-bit executable? If so, it probably won't run on your 32-bit system. What does 'file snapbdf' report?

JP

[James R. Ferguson]

Hi Gino:

You increased 'maxssiz' which was probably not the culprit. Have a look at 'maxdsiz' and/or your swapspace (with 'swapinfo -tam').

Regards!

...JRF...

[Steven E. Protter]

1) Increase swap if possible. I am interested in the swapinfo -tam output.

2) Analyze the core dump with q4 and see if you learn anything about the actual cause. Attaching instructions.

3) Do other applications complain about this? It could be the snapbdf that has the problem, q4 might help you figure it out.

SEP

[Gino Castoldi_2]

Hi,

Here is the output from a
# file snapbdf

snapbdf: PA-RISC1.1 shared executable dynamically linked

Is there another way to tell if it's a 32 and/or 64bit
executable?


Here's the output from
# swapinfo -tam

Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1024 0 1024 0% 0 - 1 /dev/vg00/lvol2
reserve - 255 -255
memory 999 401 598 40%
total 2023 656 1367 32% - 0 -

It looks like there's 598MB of free memory available.

I will check into increasing
'maxdsiz' and I will run
'chatr' with the different options.

10 points to any good answer.
Thank you
Gino

[Stefan Farrelly]

PA-RISC1.1 is a 32bit binary. If it was 64bit it would say ELF-64. So snapbdf will execute on 32 or 64bit OS.

Your swapinfo dev USED line is 0 which means its not a swap issue.

maxdsiz increase should fix it.