From: Benjamin ROUZAUD <brouzaud@numalliance.com>
To: xenomai@xenomai.org
Subject: [Xenomai] Fwd: rt,Heap segfault with unittest
Date: Thu, 01 Dec 2016 16:21:07 +0100 [thread overview]
Message-ID: <58403FE3.50701@numalliance.com> (raw)
In-Reply-To: <583D46A3.7010206@numalliance.com>
Hello,
We made a new 32 bits system with xeno v3.0.3 .
first question, do we need to switch to git/next branch or keep it ?
During the execution of program using the library xenomai, we met a
problem about allocation memory between two process. Indeed, with a same
session, one program create the differents areas of memories but the
next try and fail. We create a unittest case that reproduces the bug between the
two process. But , since the problem has happened "randomly", depending on running context, we hope you will be able to
reproduce it.
Xenomai is configure with this flags : --enable-smp, --enable-pshared
--enable-dlopen-libs --enable-tls
You will found the differents files at google drive (cf https://drive.google.com/drive/folders/0B7MmKH2j6iMYWjJfTzVOcFVTRDQ?usp=sharing).
You will find modification of /alchemy/heap.c file trying to
search for the error at processing time. (cf enclosed heap.txt file)
You will find too the two tests programs with a makefile in enclosed heaptest.tar.gz file. The process B
create differents allocation areas and pauses.
projetB --session=t
the process C tries to create or link differents allocation areas but it crashes with segfault after many
creation.
projetC --session=t
Cordially,
B. Rouzaud
R&D Numalliance
next parent reply other threads:[~2016-12-01 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <583D46A3.7010206@numalliance.com>
2016-12-01 15:21 ` Benjamin ROUZAUD [this message]
2016-12-03 17:16 ` [Xenomai] Fwd: rt,Heap segfault with unittest Philippe Gerum
2016-12-27 15:20 ` Philippe Gerum
[not found] <585798F8.1060309@numalliance.com>
2016-12-20 10:07 ` Benjamin ROUZAUD
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=58403FE3.50701@numalliance.com \
--to=brouzaud@numalliance.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.