linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org" <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org"
	<carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org>,
	"aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] exit.3: ATTRIBUTES: Note function that is not thread-safe
Date: Tue, 25 Mar 2014 02:56:23 +0000	[thread overview]
Message-ID: <5330EFBD.6010108@cn.fujitsu.com> (raw)
In-Reply-To: <51998AC5.3070803-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>


On 05/20/2013 10:30 AM, Peng Haitao wrote:
> 
> On 05/19/2013 02:30 AM, Michael Kerrisk wrote:
>>
>> Ouch! Really? so one cannot call exit(3) from a multithreaded program?
>> This seems a clear violation of the standard. 
>>
> 
> Yes.
> I make a test program to test exit(3) which is not thread-safe.
> 
> $ gcc -o exit exit.c -lpthread
> $ ./exit
> Goodbye.
> ...
> Goodbye.
> Segmentation fault
> 
>> Could you provide some pointers to more information on this point (e.g., URL
>> of mail thread archive discussions.)
>>
> 

In glibc manual, exit() is also MT-Unsafe.
I will send v2 patch with update the date in the TH line.

http://www.gnu.org/software/libc/manual/html_mono/libc.html#Normal-Termination


-- 
Best Regards,
Peng

> http://sourceware.org/ml/libc-alpha/2013-03/msg00004.html
> 
> 

      parent reply	other threads:[~2014-03-25  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  9:18 [PATCH] exit.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
     [not found] ` <1367572694-21931-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:30   ` Michael Kerrisk
     [not found]     ` <5197C8C4.3060205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-20  2:30       ` Peng Haitao
     [not found]         ` <51998AC5.3070803-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-03-25  2:56           ` penght-BthXqXjhjHXQFUHtdCDX3A [this message]

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=5330EFBD.6010108@cn.fujitsu.com \
    --to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
    --cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).