mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linux err <linux_err@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Core file size?
Date: Fri, 1 Dec 2006 07:47:34 -0800 (PST)	[thread overview]
Message-ID: <236282.74568.qm@web56515.mail.re3.yahoo.com> (raw)
In-Reply-To: <9a8748490612010640t7ed7119bj57f45c8b47289719@mail.gmail.com>

This patch fixed it.

http://lkml.org/lkml/2005/6/13/204

The ELF core dump code has one use of off_t when
writing out segments.  Some
of the segments may be passed the 2GB limit of an
off_t, even on a 32-bit
system, so it's important to use loff_t instead.  This
fixes a corrupted
core dump in the bigcore test in GDB's testsuite.

Signed-off-by: Daniel Jacobowitz
<dan@codesourcery.com>

Index: linux-2.6.11/fs/binfmt_elf.c
===================================================================
--- linux-2.6.11.orig/fs/binfmt_elf.c	2005-06-09
16:38:17.000000000 -0400
+++ linux-2.6.11/fs/binfmt_elf.c	2005-06-10
00:10:52.000000000 -0400
@@ -1125,7 +1125,7 @@ static int dump_write(struct
file *file,
 	return file->f_op->write(file, addr, nr,
&file->f_pos) == nr;
 }
 
-static int dump_seek(struct file *file, off_t off)
+static int dump_seek(struct file *file, loff_t off)
 {
 	if (file->f_op->llseek) {
 		if (file->f_op->llseek(file, off, 0) != off)
-- 




--- Jesper Juhl <jesper.juhl@gmail.com> wrote:

> On 30/11/06, linux err <linux_err@yahoo.com> wrote:
> > Does anyone know what determines the size of a
> core
> > dump? I have a process running out of memory (it
> > allocates about 3GB) - but the size of core varies
> > (between 2-3GB) depending on how much the process
> > wrote on the allocated memory.
> >
> 
> Makes perfect sense. The core dump contains the
> memory of the process,
> so if the process has 3GB in use then the core file
> will be 3GB.
> 
> You can limit the size of core dumps with "ulimit
> -c"
> 
> 
> > Also, the time it takes to write the core (same
> size)
> > varies??
> >
> Could be many reasons for that. If the load on the
> machine varies the
> time to perform any given action will vary as well.
> 
> 
> > I briefly looked at elf_core_dump and
> get_user_pages()
> > in binfmt_elf.c. Is there any documentation on
> this?
> > Or anyone knows how it works?
> >
> http://x86.ddj.com/ftp/manuals/tools/elf.pdf
> http://en.wikipedia.org/wiki/Core_dump
> 
> 
> -- 
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post 
> http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please     
> http://www.expita.com/nomime.html
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

      reply	other threads:[~2006-12-01 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  4:44 linux err
2006-12-01 14:40 ` Jesper Juhl
2006-12-01 15:47   ` linux err [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=236282.74568.qm@web56515.mail.re3.yahoo.com \
    --to=linux_err@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®