This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: shm_open failed:Invalid argument in glibc 2.20
- From: Cui Bixuan <cuibixuan at huawei dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Mon, 22 Feb 2016 11:34:37 +0800
- Subject: Re: shm_open failed:Invalid argument in glibc 2.20
- Authentication-results: sourceware.org; auth=none
- References: <56C52C92 dot 2010901 at huawei dot com> <CAE2sS1hF7yrWHri4Qhsmg932gBvsP6mMJ=J-Dj9xDR6zbUiy8g at mail dot gmail dot com>
On 2016/2/19 2:08, Carlos O'Donell wrote:
> On Wed, Feb 17, 2016 at 9:29 PM, Cui Bixuan <cuibixuan@huawei.com> wrote:
>> fd = shm_open("./a", O_RDWR|O_CREAT, 00700);
>
> This is an invalid shared memory object name for the glibc implementation.
>
> Slashes that are not the first slash are implementation defined.
>
> The glibc manual clearly states:
> ~~~
> In the GNU C Library it must be a string smaller than NAME_MAX bytes starting
> with an optional slash but containing no other slashes.
> ~~~
>
Thank you very much.
> The fix that restricts this was for this bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=15763
>
> Cheers,
> Carlos.
>
>