This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: how do exit and _exit affect mmapped memory?

From: Ángel González <keisial at gmail dot com>
To: Godmar Back <godmar at gmail dot com>
Cc: Dmitry Goncharov <dgoncharov at users dot sf dot net>, libc-help at sourceware dot org
Date: Sun, 09 Sep 2012 17:24:33 +0200
Subject: Re: how do exit and _exit affect mmapped memory?
References: <20120909031203.GC10479@madrid> <CAB4+JYKgnhpsYB=hnZ_APzJoPg6ppEQt+Cbgd2vW2iD3A1CEYg@mail.gmail.com>

On 09/09/12 06:32, Godmar Back wrote:
> It'll be saved in all cases, no matter what the process does or how it exits.
>
>  - Godmar
Assuming the OS doesn't crash after that before it updates the file on
disk :)

Which is highly unlikely, if you need to protect against that
eventuality, call msync()

Follow-Ups:
- Re: how do exit and _exit affect mmapped memory?
  - From: Dmitry Goncharov

References:
- how do exit and _exit affect mmapped memory?
  - From: Dmitry Goncharov
- Re: how do exit and _exit affect mmapped memory?
  - From: Godmar Back

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]