From: Peter Niemayer <niemayer@isg.de>
To: cr@sap.com
Cc: linux-kernel@vger.kernel.org
Subject: unused shared memory is written into core dump - the bug is back again...
Date: Mon, 06 May 2002 20:47:12 +0200 [thread overview]
Message-ID: <3CD6CFB0.FB57BA04@isg.de> (raw)
Christoph Roland 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.
Well, it was fixed (thanks!) back then in June 2001.
However, the misbehaviour has returned - I can't say exactly when,
but with 2.4.18 it happenes again and just caused my computer to
hang for quite a long time (dumping 10 cores of empty 512 MB per process
takes some time... :-| )
Can you fix it again (and set up a booby-trap in the source that immediately
electro-shocks anyone trying to revert to the old bad habit)? :-)
Regards,
Peter Niemayer
reply other threads:[~2002-05-06 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CD6CFB0.FB57BA04@isg.de \
--to=niemayer@isg.de \
--cc=cr@sap.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 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.