[Crash-utility] EFBIG with gdb - to you hack gdb to pass O_LARGEFILE in the files open() flags?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dave: I was wondering why gdb isn't having a problem with the crash file being too big when started with crash yet when handing the vmcore directly to gdb it gets an error while opening the file EFBIG. Did you hack gdb to get around this. Seems to be done on 32 bit code when file is too large. Looks like the system call will ignore this if O_LARGEFILE is set: - ------------------------------------------------------------------------- /* ~ * Called when an inode is about to be open. ~ * We use this to disallow opening large files on 32bit systems if ~ * the caller didn't specify O_LARGEFILE. On 64bit systems we force ~ * on this flag in sys_open. ~ */ int generic_file_open(struct inode * inode, struct file * filp) { ~ if (!(filp->f_flags & O_LARGEFILE) && i_size_read(inode) > MAX_NON_LFS) ~ return -EFBIG; ~ return 0; } - --------------------------------------------------------------------------- The system making the core file is likely running in 32 bit mode but it has a lot of memory, likely 4GB. MemTotal: 3,557,132 kB This old 2.6.16 kernel doesn't know that the processor can run in 64 bit mode. Both gdb and crash were build in the same 'build' env and appear to be the same version. - -piet