From: "Stéphane ANCELOT" <sancelot@free.fr>
To: Philippe Gerum <rpm@xenomai.org>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xenomai 3.0rc4 rt_heap_alloc replies with timeout
Date: Tue, 05 May 2015 15:37:40 +0200 [thread overview]
Message-ID: <5548C7A4.5030309@free.fr> (raw)
In-Reply-To: <5542205E.5080302@free.fr>
Hi,
unfortunately, There is something wrong for unknown reason using these
functions.
I made a simple regression program that only create heaps and allocates
area.
At line 190 of the file, depending on the size value of the heap, the
program works or not.
This looks like corrupted memory problem...
enclose is the c file, I hope you will be able reproduce it.
Regards,
Steph
On 30/04/2015 14:30, Stéphane ANCELOT wrote:
> On 30/04/2015 10:34, Philippe Gerum wrote:
>> On 04/30/2015 09:08 AM, Stéphane ANCELOT wrote:
>>> Hi,
>>>
>>> Ok, I am using more than one heap, it seems being related .
>>>
>> I don't think so. This unit test illustrates such case:
>> http://git.xenomai.org/xenomai-3.git/commit/?h=next&id=fc7a90768c60e59cdc86ed47a42d4757ff2c4d90
>>
>>
> Yes, this one rocks.
>
> I found the reason in my application, I created the heap with H_SINGLE
> (or deprecated H_SHARED)
> but the block is not being allocated if rt_heap_alloc() func size
> parameter is 0 .
> changing size to blocksize works.
>>> It is not possible anymore?
>> That would be quite a silly decision, isn't it? You should refer to this
>> part of the online migration guide to find out which changes have been
>> introduced in the user-visible interface:
>>
>> http://xenomai.org/migrating-from-xenomai-2-x-to-3-x/#Heaps
>>
>>> Regards,
>>> S.Ancelot
>>>
>>>
>>>
>>> On 28/04/2015 19:25, Philippe Gerum wrote:
>>>> On 04/28/2015 05:50 PM, Stéphane ANCELOT wrote:
>>>>> Hi,
>>>>>
>>>>> for unknown reason, using compat api, rt_heap_alloc replies with
>>>>> timeout, or blocks if TM_INFINITE is requested.
>>>> Because the request exceeds the available space. The compat api
>>>> does not
>>>> wrap rt_heap services, so this is unrelated.
>>>>
>>>>> I also noticed I don't have /dev/rtheap node, is it normal.?
>>>>>
>>>> Yes, /dev/rtheap is gone in 3.x.
>>>>
>>>
>>
>
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://www.xenomai.org/mailman/listinfo/xenomai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: heap_test.cpp
Type: text/x-c++src
Size: 6429 bytes
Desc: not available
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150505/44cda4a1/attachment.cpp>
next prev parent reply other threads:[~2015-05-05 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 15:50 [Xenomai] xenomai 3.0rc4 rt_heap_alloc replies with timeout Stéphane ANCELOT
2015-04-28 17:25 ` Philippe Gerum
2015-04-30 7:08 ` Stéphane ANCELOT
2015-04-30 8:34 ` Philippe Gerum
2015-04-30 12:30 ` Stéphane ANCELOT
2015-05-05 13:37 ` Stéphane ANCELOT [this message]
2015-05-05 17:21 ` Gilles Chanteperdrix
2015-05-06 8:21 ` Stéphane ANCELOT
2015-05-06 8:23 ` Gilles Chanteperdrix
2015-05-06 8:26 ` Gilles Chanteperdrix
2015-05-06 8:31 ` Stéphane ANCELOT
2015-05-06 8:48 ` Gilles Chanteperdrix
2015-05-06 9:14 ` Philippe Gerum
2015-05-06 8:56 ` Philippe Gerum
2015-05-06 9:55 ` Stéphane ANCELOT
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=5548C7A4.5030309@free.fr \
--to=sancelot@free.fr \
--cc=rpm@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.