All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Stéphane ANCELOT" <sancelot@free.fr>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xenomai 3.0rc4 rt_heap_alloc replies with timeout
Date: Wed, 6 May 2015 10:48:14 +0200	[thread overview]
Message-ID: <20150506084814.GV1993@hermes.click-hack.org> (raw)
In-Reply-To: <5549D15A.6060601@free.fr>

On Wed, May 06, 2015 at 10:31:22AM +0200, Stéphane ANCELOT wrote:
> On 06/05/2015 10:26, Gilles Chanteperdrix wrote:
> >On Wed, May 06, 2015 at 10:21:18AM +0200, Stéphane ANCELOT wrote:
> >>     size = 824; // size = 824 is failing but changing size to 3200 rocks ...
> >>     // --------------------------------------------------------------
> >>     ret = rt_heap_create(&heap2, "config", size, flags);
> >>     traceobj_assert(&trobj, ret == 0);
> >The interesting call to rt_heap_inquire would go here.
> >
> >All the other ones are irrelevant.
> >
> >Also, have you tried directly creating the heap with the failing
> >size instead of doing it after creating many useless heaps? Just to
> >reduce the test case.
> >
> >
> >>     cout << " heap size : " << info.heapsize << " heap usablemem: " <<
> >>info.usablemem;
> >The value you print here do not correspond to the heap you just
> >created. What is the point of this ?
> >
> >>     ret = rt_heap_alloc(&heap2, size, TM_INFINITE, &p);
> >>     traceobj_assert(&trobj, ret == 0);
> >>
> >>     exit(0);
> >>}
> >>
> >>
> You are right, reducing the test case, and using this size reports the
> problem :

This is basic: always try to reduce the test case to be as simple as
possible in order to reduce where to search for the problem. Also
note that a memory corruption is even less likely than with your
previous test case.

> 
> 
> 
> 
> output:
> root@debian:/home/macsoft# ./heap_regression
>    0"002.074| BUG: [main] trace assertion failed:
> ../heap_test.cpp:34 => "ret == 0"

Ok, so, in fact the heap creation fails when size is 824, not the
heap allocation. Sorry, from the thread subject I had understood
rt_heap_alloc was failing. Also, this is a general thing about error
returns: in general the value indicate the reason for the failure.
Maybe you could print it?

-- 
					    Gilles.


  reply	other threads:[~2015-05-06  8:48 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
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 [this message]
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=20150506084814.GV1993@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=sancelot@free.fr \
    --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.