All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : Make xnarch_init_timeconv an uninlined weak function
Date: Thu, 11 Feb 2010 18:04:26 +0100	[thread overview]
Message-ID: <4B74389A.80300@domain.hid> (raw)
In-Reply-To: <4B743359.8030709@domain.hid>

Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> And instantly - you forget about dlopen scenarios which triggered the
>>>>> bug in timeconv.
>>>> I do not see why dlopen would trigger a bug. Could you explain it?
>>> If you dlopen, say, libnative and call a symbol that uses some timeconv
>>> constants, you have to make sure that the init code of libnative
>>> initializes those variables that are later used.
>> That is where I do not follow you. dlopen is called after the startup of
>> the other libs, so either it references its own variables, which are
>> initialized once its constructor has been called. Or it references the
>> variables of the posix lib (only native and posix use timeconv in
>> user-space) which is already initialized.
> 
> In this case, dlopen was part of some constructor, and the ordering
> turned out to be "unfortunate".

Ok. Got it now. Will test your patch, but I will probably leave the weak
attribute to the shared functions.

-- 
					    Gilles.


  reply	other threads:[~2010-02-11 17:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NfBdX-0001ga-4b@domain.hid>
2010-02-10 12:34 ` [Xenomai-core] [Xenomai-git] Jan Kiszka : Make xnarch_init_timeconv an uninlined weak function Gilles Chanteperdrix
2010-02-10 12:43   ` Jan Kiszka
2010-02-10 14:01     ` Gilles Chanteperdrix
2010-02-10 14:48       ` Philippe Gerum
2010-02-10 19:33     ` Gilles Chanteperdrix
2010-02-10 20:24       ` Jan Kiszka
2010-02-10 20:33         ` Gilles Chanteperdrix
2010-02-10 21:09           ` Jan Kiszka
2010-02-10 21:13             ` Gilles Chanteperdrix
2010-02-10 21:23               ` Jan Kiszka
2010-02-10 21:26                 ` Gilles Chanteperdrix
2010-02-10 21:34                   ` Jan Kiszka
2010-02-10 21:39                     ` Gilles Chanteperdrix
2010-02-11  8:38                       ` Jan Kiszka
2010-02-11  8:47                         ` Gilles Chanteperdrix
2010-02-11  9:37                           ` Jan Kiszka
2010-02-11  9:46                             ` Gilles Chanteperdrix
2010-02-11 10:36                               ` Jan Kiszka
2010-02-11 11:04                                 ` Gilles Chanteperdrix
2010-02-11 14:14                                   ` Jan Kiszka
2010-02-11 15:59                                     ` Gilles Chanteperdrix
2010-02-11 16:13                                       ` Jan Kiszka
2010-02-11 16:16                                         ` Gilles Chanteperdrix
2010-02-11 16:42                                           ` Jan Kiszka
2010-02-11 17:04                                             ` Gilles Chanteperdrix [this message]
2010-02-11 17:10                                               ` Jan Kiszka
2010-02-10 21:28                 ` Gilles Chanteperdrix
2010-02-10 21:35                   ` Jan Kiszka

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=4B74389A.80300@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    --cc=jan.kiszka@domain.hid \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.