* unused shared memory is written into core dump - the bug is back again...
@ 2002-05-06 18:47 Peter Niemayer
0 siblings, 0 replies; only message in thread
From: Peter Niemayer @ 2002-05-06 18:47 UTC (permalink / raw)
To: cr; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-05-06 18:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-06 18:47 unused shared memory is written into core dump - the bug is back again Peter Niemayer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox