libsanitizer merge from upstream r208536
Paolo Carlini
paolo.carlini@oracle.com
Fri May 23 09:27:00 GMT 2014
Hi,
On 05/23/2014 11:21 AM, Yury Gribov wrote:
>>> I've checked all available systems and wasn't able to repro this.
>>
>> Given your exchanges with Jakub I thought that at this point it was
>> clear that the issue is real.
>
> There are three issues here:
> 1) whether warning should cause termination
> 2) whether warning should be displayed by default
> 3) why warning occurs on your machine
>
> We mainly discussed 1 and 2 with Jakub but even if we hide this
> warning it still should have come up on your machine in the first place.
> It's either false positive which needs to be fixed or symptom of some
> real problem. I believe it still makes sense to investigate the
> original problem.
>
>>> Every time vDSO was already filtered with
>>>
>>> if (!info->dlpi_name || info->dlpi_name[0] == 0)
>>> return 0;
>>>
>>> in FindFirstDSOCallback.
>>>
>>> Could you provide additional details of your setup? Or perhaps print
>>> dlpi_name of offending library?
>>
>> How do I print dlpi_name?
>
> Could you add something like
> Report("'%s'\n", info->dlpi_name);
> after
> if (!info->dlpi_name || info->dlpi_name[0] == 0)
> check in FindFirstDSOCallback? This should give us the name of library
> which causes problems.
It's always linux-vdso.so.1, but wasn't that already known, given the
ldd requested by Jakub?!?
Paolo.
More information about the Gcc-patches
mailing list