This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Are syconf(_SC_XXX) issues glibc or kernel issues?
- From: Jeffrey Walton <noloader at gmail dot com>
- To: Jason Duerstock <jason dot duerstock at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Wed, 21 Mar 2018 14:21:42 -0400
- Subject: Re: Are syconf(_SC_XXX) issues glibc or kernel issues?
- References: <CAP5F8c+81S-pD2OV7GK21fa3i-L5W4WEHfZm9xs6ORdWCmiUAA@mail.gmail.com>
- Reply-to: noloader at gmail dot com
On Wed, Mar 21, 2018 at 12:38 PM, Jason Duerstock
<jason.duerstock@gmail.com> wrote:
> Run strace against the binary. If the syscall returns the "correct"
> value(s), then it's a glibc issue. If not, it's a kernel issue.
Thanks Jason.
If I _don't_ see a system call, then would that indicate it is
probably a glibc issue? That is, glibc provides the answer without
going to the kernel?
Jeff
> On Wed, Mar 21, 2018 at 12:30 PM, Jeffrey Walton <noloader@gmail.com> wrote:
>> Hi Everyone,
>>
>> My apologies for asking. I'm seeing bug reports against both components.
>>
>> Are syconf(_SC_XXX) issues glibc or kernel issues?
>>
>> In my particular case, I'm getting an unexpected value from
>> _SC_LEVEL1_DCACHE_LINESIZE on PPC64. AIX and SC_L1C_DLS returns an
>> expected value.
>>
>> Jeff