All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Yet another ((weak)) bug
Date: Fri, 12 Feb 2010 16:21:59 +0100	[thread overview]
Message-ID: <4B757217.3060406@domain.hid> (raw)

Hi Gilles,

this one requires some fixing too:

xeno_sem_heap is marked weak. xeno_init_sem_heaps is called once per
initialized skin. It unmaps any existing heap and creates a new one.
That's already fragile during constructor run, but it's lethal during
process runtime, ie. when using dlopen.

I think the solution is to handle forks separately and only remap in
that case. Digging in this direction now.

BTW, what triggers the re-run of xeno_init_sem_heaps after a fork so far?

Jan

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


             reply	other threads:[~2010-02-12 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 15:21 Jan Kiszka [this message]
2010-02-12 15:25 ` [Xenomai-core] Yet another ((weak)) bug Gilles Chanteperdrix
2010-02-12 15:37   ` Jan Kiszka
2010-02-12 15:54     ` Gilles Chanteperdrix
2010-02-12 16:45       ` Jan Kiszka
2010-02-12 16:03     ` Gilles Chanteperdrix
2010-02-12 16:22       ` Jan Kiszka
2010-02-12 16:29         ` Stefan Kisdaroczi
2010-02-12 21:14           ` Gilles Chanteperdrix
2010-02-24 13:18             ` Jan Kiszka
2010-02-24 14:08               ` Gilles Chanteperdrix
2010-03-01 14:00                 ` Jan Kiszka
2010-03-01 14:02                   ` Gilles Chanteperdrix
2010-03-01 14:05                     ` Jan Kiszka
2010-03-02  0:13                       ` Gilles Chanteperdrix

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=4B757217.3060406@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.org \
    /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.