From: Christoph Rohland <cr@sap.com>
To: Peter Niemayer <niemayer.viag@isg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unused shared memory is written into core dump - bug or feature?
Date: 12 Jun 2001 16:56:29 +0200 [thread overview]
Message-ID: <m3ae3d7nmq.fsf@linux.local> (raw)
In-Reply-To: <3B262158.29EFC01A@isg.de>
In-Reply-To: Peter Niemayer's message of "Tue, 12 Jun 2001 16:04:08 +0200"
Hi Peter,
On Tue, 12 Jun 2001, Peter Niemayer wrote:
> I just noticed that when I attach some SYSV shared memory segments
> to my process and then that process dies from a SIGSEGV that _all_
> the shared memory is dumped into the core file, even if it was never
> used and therefore didn't show up in any of the memory statistics.
Fixed in recent kernel versions (2.2 and 2.4). It will create sparse
files and not touch the unused address space.
Greetings
Christoph
next prev parent reply other threads:[~2001-06-12 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 14:04 unused shared memory is written into core dump - bug or feature? Peter Niemayer
2001-06-12 14:56 ` Christoph Rohland [this message]
2001-06-12 16:01 ` Alan Cox
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=m3ae3d7nmq.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niemayer.viag@isg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.