Re: [Xenomai-core] __wrap_clock_gettime

[Jan Kiszka <jan.kiszka@domain.hid>]

On 2011-07-27 20:49, Gilles Chanteperdrix wrote:
> On 07/22/2011 05:04 PM, Jan Kiszka wrote:
>> Hi Gilles,
>>
>> pulling assert_context.c into the common libxenomai created a problem
>> around picking the right __wrap_clock_gettime. As libpthread_rt depends
>> on libxenomai, the latter is loaded first and defines the debug version
>> of __wrap_clock_gettime as the default. There is no chance to pull the
>> posix skin implementation.
>>
>> I don't have a nice idea yes how to resolve this. Options are:
>>  - drop __wrap_clock_gettime from assert_context.c (affects any skin
>>    user != posix)
>>  - put assert_context stuff into separate library again
>>  - put __wrap_clock_gettime in all skin libs != posix
>>
>> I'm favoring the simplest approach ATM, ie. the first one. Other ideas?
> 
> I agree, but I would have thought __attriibute__((weak)) takes care of
> this issue.

The point is that once you have pulled in that weak symbol into a
process, the dynamic loader won't update it if a non-weak version is
pulled in via dlopen.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux