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: pthread_exit behavior from main

From: "Carlos O'Donell" <carlos at systemhalted dot org>
To: Godmar Back <godmar at gmail dot com>
Cc: Bharath Ramesh <bramesh at vt dot edu>, libc-help at sourceware dot org
Date: Thu, 4 Oct 2012 21:51:32 -0400
Subject: Re: pthread_exit behavior from main
References: <20121004220540.GI3182@vt.edu><CAE2sS1gGmQc=oGe29TQ2VDyoihM90s7Z_K6Zg3LGdTrn0T_75g@mail.gmail.com><CAB4+JY+tUXDQX8+vhJ_S-_Jq_GynNMoKOfMZ3bTgP+4juXh1Fw@mail.gmail.com>

On Thu, Oct 4, 2012 at 9:41 PM, Godmar Back <godmar@gmail.com> wrote:
> On Thu, Oct 4, 2012 at 9:09 PM, Carlos O'Donell <carlos@systemhalted.org> wrote:
>>
>> You are seeing the undefined results of reading memory that the
>> runtime has marked with madvise as MADV_DONTNEED.
>>
>
> Just out of curiosity, why do you madvise it with MADV_DONTNEED rather
> than munmapping it outright?

That's a very good question and I don't have a good answer.

I would not object to someone doing an analysis of the pro's and con's
and posting a patch.

Perhaps there is actually a language or POSIX requirement that I'm not
aware of.

Cheers,
Carlos.

Follow-Ups:
- Re: pthread_exit behavior from main
  - From: Godmar Back

References:
- pthread_exit behavior from main
  - From: Bharath Ramesh
- Re: pthread_exit behavior from main
  - From: Carlos O'Donell
- Re: pthread_exit behavior from main
  - From: Godmar Back

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