From: Daniel Jacobowitz <dan@debian.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs/binfmt_elf.c:maydump()
Date: Fri, 7 Apr 2006 14:02:43 -0400 [thread overview]
Message-ID: <20060407180243.GA27828@nevyn.them.org> (raw)
In-Reply-To: <20060406.221807.114721185.davem@davemloft.net>
On Thu, Apr 06, 2006 at 10:18:07PM -0700, David S. Miller wrote:
> How about something like the following patch? If it's executable
> and not written to, skip it. This would skip the main executable
> image and all text segments of the shared libraries mapped in.
Will this dump text segments that have been COW'd for the purposes of
inserting a breakpoint?
It's just a question of goals, I guess. We could dump code, but it's
rarely useful, so historically we didn't. Similarly, we could dump
mapped data from shared memory, but it can be huge and is rarely
useful, so generally we don't.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-07 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 21:03 fs/binfmt_elf.c:maydump() David S. Miller
2006-04-06 22:15 ` fs/binfmt_elf.c:maydump() Daniel Jacobowitz
2006-04-06 22:35 ` fs/binfmt_elf.c:maydump() David S. Miller
2006-04-07 5:18 ` fs/binfmt_elf.c:maydump() David S. Miller
2006-04-07 18:02 ` Daniel Jacobowitz [this message]
2006-04-07 20:27 ` fs/binfmt_elf.c:maydump() David S. Miller
2006-04-10 13:01 ` fs/binfmt_elf.c:maydump() Daniel Jacobowitz
2007-01-03 2:02 ` Contents of core dumps (was: Re: fs/binfmt_elf.c:maydump()) Daniel Jacobowitz
2007-01-03 4:57 ` Contents of core dumps David Miller
2007-01-03 18:13 ` Daniel Jacobowitz
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=20060407180243.GA27828@nevyn.them.org \
--to=dan@debian.org \
--cc=davem@davemloft.net \
--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