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] Warning when compiling trunk.
Date: Mon, 20 Oct 2008 23:06:42 +0200 [thread overview]
Message-ID: <48FCF2E2.8050809@domain.hid> (raw)
In-Reply-To: <48FCF14C.8050103@domain.hid>
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> Gilles Chanteperdrix wrote:
>>>>>> I get this warning when compiling trunk:
>>>>>>
>>>>>> checking for __thread... rm: cannot remove `conftest1.dir': Is a directory
>>>>>> yes
>>>>>>
>>>>> That simple, it's a typo in this line:
>>>>>
>>>>> http://www.rts.uni-hannover.de/xenomai/lxr/source/configure.in?v=SVN-trunk#394
>>>>>
>>>>> Also, that rm should be done outside the if block to play safe.
>>>> Ok. But once this is fixed, I get a segmentation fault with __thread on
>>>> ARM in rt_task_trampoline. I am currently testing the SIGWINCH thing,
>>>> and if __thread is disabled, there is no segfault.
>>> If a #ifdef 0 xeno_set_current, there is no segfault.
>>>
>> Interesting. What about removing the initial-exec attributes? Is
>> __thread otherwise know to work on your platform?
>
> Yes. This is a race condition, the real bug is, IMHO:
> __native_self = *iargs->task;
> When the segfault happens iargs->task is NULL. I suspect you are not
> supposed to use iargs after the __native_task_create syscall.
Yes, that was the problem.
However, another problem, should not the __thread variables be given the
weak attribute too? If a native thread tries to use a pthread mutex, I
want pthread_mutex_lock to obtain the current xnhandle_t set by the
native skin, not an inexistant one that should have been set by the
posix skin but obviously has not.
--
Gilles.
next prev parent reply other threads:[~2008-10-20 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 19:30 [Xenomai-core] Warning when compiling trunk Gilles Chanteperdrix
2008-10-20 20:03 ` Jan Kiszka
2008-10-20 20:34 ` Gilles Chanteperdrix
2008-10-20 20:37 ` Gilles Chanteperdrix
2008-10-20 20:42 ` Jan Kiszka
2008-10-20 20:59 ` Gilles Chanteperdrix
2008-10-20 21:06 ` Gilles Chanteperdrix [this message]
2008-10-20 21:15 ` Jan Kiszka
2008-10-20 21:25 ` Gilles Chanteperdrix
2008-10-20 21:30 ` Jan Kiszka
2008-10-20 21:32 ` Gilles Chanteperdrix
2008-10-20 21:34 ` Jan Kiszka
2008-10-20 21:35 ` Gilles Chanteperdrix
2008-10-20 22:41 ` Jan Kiszka
2008-10-20 22:48 ` Gilles Chanteperdrix
2008-10-20 23:18 ` Gilles Chanteperdrix
2008-10-21 6:31 ` Jan Kiszka
2008-10-21 7:36 ` Philippe Gerum
2008-10-21 8:24 ` Jan Kiszka
2008-10-20 21:12 ` 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=48FCF2E2.8050809@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.