limitation on core file size

[DeafFrog]

Hi ,

    One one of the system running v3 , ulimit for a user is as follows :
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         3145728
stack(kbytes)        131072
memory(kbytes)       unlimited
coredump(blocks)     4194303
nofiles(descriptors) 8192

Now , then a process of this user gives a coredump , every time the core file is not grater than 666 Mb.
when we do a gbd on these core it says "core is truncated.The common reason for truncation include system limit on core size
and lack of disk space". Now the latter , ie lack of disk space is not the issue the FS is having enough space.

1) Whad could have been rescriting the core generation to 666 mb only .
2) the core generated by this user process can be upoto 2Gb , correct ?

Regards,

[Dennis Handly]

>every time the core file is not greater than 666 Mb.

Is this PA or Integrity?  Is this 32 or 64 bit application?

>when we do a gdb on these core it says "core is truncated. ..."

If you have an ELF core file, you should get the structure with:

elfdump -S -o core

>1) What could have been restricting the core generation to 666 Mb only .
>2) the core generated by this user process can be upto 2 Gb, correct?

Yes, it should allow you 4,194,303 * 512 bytes.

[DeafFrog]

Hi Dennis , it's and HPUX B.11.31 U ia64 . The application is 64 bit : ELF-32 executable object file - IA64 . Thsi is what is get if i go a elfdump : elfdump: Bad type: 1831 (elfdumperr 3003) elfdump: Bad type: 1831 (elfdumperr 3003) Regards ,

[Dennis Handly]

>The application is 64 bit: ELF-32 executable object file - IA64.

No, the application is 32 bit (ELF-32).

>This is what I get if I do a elfdump: elfdump: Bad type: 1831

It looks like it was corrupted because of the truncation.

[DeafFrog]

Hi Dennis ,

                     Any OS parameter that could have restricted the size of core generation to a limited size only.

Regards,

[Dennis Handly]

>Any OS parameter that could have restricted the size of core generation to a limited size only.

That should show up on "ulimit -c".  Why not change it to "unlimited" and try again?