All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] [PATCH 0/3] dlopen testcase
Date: Tue, 24 Apr 2018 14:37:42 +0200	[thread overview]
Message-ID: <20180424123745.7015-1-henning.schild@siemens.com> (raw)

The test binary was actually linked as a xenomai binary, so the test did
not actually cover the "cold" init phase.
Turns out that in fact dlclose will not truly work, because we lack
destructors for the init functions of the so called setup_descriptors.

So first revert the patch introducing destructors. We do not have code
to destruct, dont even pretent by addressing a fraction of the whole
problem.

Second change the linker flags and make the testcase cover cold init.
Remove the calls to dlclose() and the re-dlopen(), because that is not
actually supported.

And last but not least, make sure a dlclose() will not actually work on
xenomai libs.

Henning Schild (3):
  Revert "boilerplate/setup: introduce destructors for __setup_call"
  smokey/dlopen: fix testcase
  build: link dlopen libs with "nodelete"

 configure.ac                              | 1 +
 include/boilerplate/setup.h               | 7 -------
 lib/boilerplate/setup.c                   | 6 ------
 testsuite/smokey/dlopen/Makefile.am       | 8 +-------
 testsuite/smokey/dlopen/dlopentest.c      | 9 ---------
 testsuite/smokey/dlopen/libalchemy-test.c | 2 +-
 6 files changed, 3 insertions(+), 30 deletions(-)

-- 
2.16.1



             reply	other threads:[~2018-04-24 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:37 Henning Schild [this message]
2018-04-24 12:37 ` [Xenomai] [PATCH 1/3] Revert "boilerplate/setup: introduce destructors for __setup_call" Henning Schild
2018-04-24 12:37 ` [Xenomai] [PATCH 2/3] smokey/dlopen: fix testcase Henning Schild
2018-04-24 12:37 ` [Xenomai] [PATCH 3/3] build: link dlopen libs with "nodelete" Henning Schild

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=20180424123745.7015-1-henning.schild@siemens.com \
    --to=henning.schild@siemens.com \
    --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.