Skip to contentSkip to conversation

Maximum core file size in Linux

DISCUSSION Amrith Kumar 2 participants 2 messages Jun 27, 2002 – Jun 28, 2002

lore
Share & tools
lore
#0 lore raw

Appears that there's an implicit 2Gb limit on the size of core files because it's being created without O_LARGEFILE.

A small change in fs/exec.c (do_coredump) gets me past the limit and I can now generate a core file in excess of 2Gb but then gdb complains that the core dump is too large ...

Looks like there's a broader underlying issue here that would involve changes to other places than I had thought would be required.

Anyone else out there run into a similar problem ? And if so, could you let me know what other things I may run into ... Also, is this something that has been fixed in a forthcoming release ?

Thanks,

/a

--
Amrith Kumar
[email protected]
508-665-6835

#include <std_disclaimer.h>
This e-mail message is for the sole use of the intended recipient(s) and may contain Netezza Corporation confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

#1 lore raw

This is likely a gdb issue. Unless you're carefull to use 64 bit functions of *seek*() and ftell(), your only able to access the first 2GB of a file. gdb may have issues here.

I don't recall the elf header but you may want to check the 32 bit elf format and see if is even capable to be used with core file that exceed 2GB. Said in anothre way there *could* be elf-header offsets that is 32 bit and try pointing beyond 2GB.

Terje

Quoted 36 lines · Amrith Kumar

Appears that there's an implicit 2Gb limit on the size of core files because it's being created without O_LARGEFILE.

A small change in fs/exec.c (do_coredump) gets me past the limit and I can now generate a core file in excess of 2Gb but then gdb complains that the core dump is too large ...

Looks like there's a broader underlying issue here that would involve changes to other places than I had thought would be required.

Anyone else out there run into a similar problem ? And if so, could you let me know what other things I may run into ... Also, is this something that has been fixed in a forthcoming release ?

Thanks,

/a

--
Amrith Kumar
[email protected]
508-665-6835

#include <std_disclaimer.h>
This e-mail message is for the sole use of the intended recipient(s) and may contain Netezza Corporation confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 10 lines
_________________________________________________________________________

Terje Eggestad                  mailto:[email protected]
Scali Scalable Linux Systems    http://www.scali.com

Olaf Helsets Vei 6              tel:    +47 22 62 89 61 (OFFICE)
P.O.Box 150, Oppsal                     +47 975 31 574  (MOBILE)
N-0619 Oslo                     fax:    +47 22 62 89 51
NORWAY            
_________________________________________________________________________