* [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
@ 2011-06-30 9:12 VEYSSIERE Nicolas
2011-06-30 9:33 ` Philippe Gerum
0 siblings, 1 reply; 6+ messages in thread
From: VEYSSIERE Nicolas @ 2011-06-30 9:12 UTC (permalink / raw)
To: xenomai@xenomai.org
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Hello,
I am asking for an already answered question from a very long time ago.
How can I use valgrind with Xenomai ?
Here (https://mail.gna.org/public/xenomai-help/2006-03/msg00072.html) Gilles C. tells us to use --enable-atomic-core
But I can't find this option. Maybe it has been renamed ?
# valgrind ./trivial-periodic
==27300== Memcheck, a memory error detector
==27300== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==27300== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==27300== Command: ./trivial-peridic
==27300==
--27300-- WARNING: unhandled syscall: 555
--27300-- You may be able to write your own handler.
--27300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--27300-- Nevertheless we consider this a bug. Please report
--27300-- it at http://valgrind.org/support/bug_reports.html.
Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled.
(modprobe xeno_native?)
==27300==
==27300== HEAP SUMMARY:
==27300== in use at exit: 0 bytes in 0 blocks
==27300== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==27300==
==27300== All heap blocks were freed -- no leaks are possible
==27300==
==27300== For counts of detected and suppressed errors, rerun with: -v
==27300== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 7)
Thanks for all.
--
Nicolas VEYSSIERE
[-- Attachment #2: Type: text/html, Size: 4943 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
2011-06-30 9:12 [Xenomai-help] Xenomai 2.5.6 with Valgrind ? VEYSSIERE Nicolas
@ 2011-06-30 9:33 ` Philippe Gerum
2011-06-30 10:13 ` VEYSSIERE Nicolas
0 siblings, 1 reply; 6+ messages in thread
From: Philippe Gerum @ 2011-06-30 9:33 UTC (permalink / raw)
To: VEYSSIERE Nicolas; +Cc: xenomai@xenomai.org
On Thu, 2011-06-30 at 11:12 +0200, VEYSSIERE Nicolas wrote:
> Hello,
>
>
>
> I am asking for an already answered question from a very long time
> ago.
>
>
>
> How can I use valgrind with Xenomai ?
>
You can't.
>
>
> Here (https://mail.gna.org/public/xenomai-help/2006-03/msg00072.html)
> Gilles C. tells us to use --enable-atomic-core
>
>
>
> But I can't find this option. Maybe it has been renamed ?
>
>
>
>
>
> # valgrind ./trivial-periodic
>
> ==27300== Memcheck, a memory error detector
>
> ==27300== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et
> al.
>
> ==27300== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright
> info
>
> ==27300== Command: ./trivial-peridic
>
> ==27300==
>
> --27300-- WARNING: unhandled syscall: 555
>
> --27300-- You may be able to write your own handler.
>
> --27300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
>
> --27300-- Nevertheless we consider this a bug. Please report
>
> --27300-- it at http://valgrind.org/support/bug_reports.html.
>
> Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled.
>
> (modprobe xeno_native?)
>
> ==27300==
>
> ==27300== HEAP SUMMARY:
>
> ==27300== in use at exit: 0 bytes in 0 blocks
>
> ==27300== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
>
> ==27300==
>
> ==27300== All heap blocks were freed -- no leaks are possible
>
> ==27300==
>
> ==27300== For counts of detected and suppressed errors, rerun with: -v
>
> ==27300== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from
> 7)
>
>
>
>
>
>
>
> Thanks for all.
>
>
>
> --
>
> Nicolas VEYSSIERE
>
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
2011-06-30 9:33 ` Philippe Gerum
@ 2011-06-30 10:13 ` VEYSSIERE Nicolas
2011-06-30 10:46 ` Gilles Chanteperdrix
0 siblings, 1 reply; 6+ messages in thread
From: VEYSSIERE Nicolas @ 2011-06-30 10:13 UTC (permalink / raw)
To: Philippe Gerum; +Cc: xenomai@xenomai.org
Ok, so is there something that can replace Valgrind and works with Xenomai ?
I am using the VxWorks skin.
--
Nicolas VEYSSIERE
-----Message d'origine-----
De : Philippe Gerum [mailto:rpm@xenomai.org]
Envoyé : jeudi 30 juin 2011 11:33
À : VEYSSIERE Nicolas
Cc : xenomai-help@gna.org
Objet : Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
On Thu, 2011-06-30 at 11:12 +0200, VEYSSIERE Nicolas wrote:
> Hello,
>
>
>
> I am asking for an already answered question from a very long time
> ago.
>
>
>
> How can I use valgrind with Xenomai ?
>
You can't.
>
>
> Here (https://mail.gna.org/public/xenomai-help/2006-03/msg00072.html)
> Gilles C. tells us to use --enable-atomic-core
>
>
>
> But I can't find this option. Maybe it has been renamed ?
>
>
>
>
>
> # valgrind ./trivial-periodic
>
> ==27300== Memcheck, a memory error detector
>
> ==27300== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et
> al.
>
> ==27300== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright
> info
>
> ==27300== Command: ./trivial-peridic
>
> ==27300==
>
> --27300-- WARNING: unhandled syscall: 555
>
> --27300-- You may be able to write your own handler.
>
> --27300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
>
> --27300-- Nevertheless we consider this a bug. Please report
>
> --27300-- it at http://valgrind.org/support/bug_reports.html.
>
> Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled.
>
> (modprobe xeno_native?)
>
> ==27300==
>
> ==27300== HEAP SUMMARY:
>
> ==27300== in use at exit: 0 bytes in 0 blocks
>
> ==27300== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
>
> ==27300==
>
> ==27300== All heap blocks were freed -- no leaks are possible
>
> ==27300==
>
> ==27300== For counts of detected and suppressed errors, rerun with: -v
>
> ==27300== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from
> 7)
>
>
>
>
>
>
>
> Thanks for all.
>
>
>
> --
>
> Nicolas VEYSSIERE
>
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@gna.org
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
2011-06-30 10:13 ` VEYSSIERE Nicolas
@ 2011-06-30 10:46 ` Gilles Chanteperdrix
2011-06-30 11:03 ` varname
0 siblings, 1 reply; 6+ messages in thread
From: Gilles Chanteperdrix @ 2011-06-30 10:46 UTC (permalink / raw)
To: VEYSSIERE Nicolas; +Cc: xenomai@xenomai.org
On 06/30/2011 12:13 PM, VEYSSIERE Nicolas wrote:
> Ok, so is there something that can replace Valgrind and works with Xenomai ?
>
> I am using the VxWorks skin.
>
You can use valgrind either with Xenomai simulator, but that will not be
easy, or with Xenomai-solo. But not with the dual-kernel version.
--
Gilles.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
2011-06-30 10:46 ` Gilles Chanteperdrix
@ 2011-06-30 11:03 ` varname
2011-06-30 13:05 ` Philippe Gerum
0 siblings, 1 reply; 6+ messages in thread
From: varname @ 2011-06-30 11:03 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai@xenomai.org
Gilles Chanteperdrix wrote:
> On 06/30/2011 12:13 PM, VEYSSIERE Nicolas wrote:
>> Ok, so is there something that can replace Valgrind and works with Xenomai ?
>>
>> I am using the VxWorks skin.
>>
> You can use valgrind either with Xenomai simulator, but that will not be
> easy, or with Xenomai-solo. But not with the dual-kernel version.
Could you comment on the status of Xenomai-solo? Last time I checked
(some 7 months ago) it was missing parts of the native skin. I also
remember the git checkout was not compilable. I'm rather interested in
using it for (automated) testing purposes, such as memory leak checking.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Xenomai 2.5.6 with Valgrind ?
2011-06-30 11:03 ` varname
@ 2011-06-30 13:05 ` Philippe Gerum
0 siblings, 0 replies; 6+ messages in thread
From: Philippe Gerum @ 2011-06-30 13:05 UTC (permalink / raw)
To: varname; +Cc: xenomai@xenomai.org
On Thu, 2011-06-30 at 13:03 +0200, varname wrote:
> Gilles Chanteperdrix wrote:
> > On 06/30/2011 12:13 PM, VEYSSIERE Nicolas wrote:
> >> Ok, so is there something that can replace Valgrind and works with Xenomai ?
> >>
> >> I am using the VxWorks skin.
> >>
> > You can use valgrind either with Xenomai simulator, but that will not be
> > easy, or with Xenomai-solo. But not with the dual-kernel version.
>
> Could you comment on the status of Xenomai-solo? Last time I checked
> (some 7 months ago) it was missing parts of the native skin. I also
> remember the git checkout was not compilable. I'm rather interested in
> using it for (automated) testing purposes, such as memory leak checking.
>
Xenomai-solo was proof of concept work, which eventually moved to the
xenomai-forge repository where the next Xenomai 3 architecture is being
developed. The development of the native API in the -solo branch is
discontinued, it will resume in another form in the -forge repo at some
point.
There is no documentation about the -forge contents yet. The survival
kit when browsing this code includes knowing that:
- it aims at providing support for both dual kernel based and
native-linux (typically PREEMPT_RT) platforms, using the largest
possible base of common code.
- most of the high level API implementation started to move to userland,
with no more API-specific kernel code. These APIs get real-time services
from the POSIX layer available with the underlying environment (dual
kernel's POSIX skin or nptl from native linux), which specifics are
hidden by an abstract service library.
- "copperplate" identifies the library which abstracts the real-time
services used by the high level APIs, so that their implementation is
not dependent on the underlying real-time core. It is a bit like the
nucleus API, but for userland client usage.
- this new architecture therefore exhibits two real-time cores, selected
at build time. The dual kernel core inherited from the Xenomai 2
architecture is nicknamed "cobalt" in the sources. The native linux core
inherited from the -solo work is called "mercury".
- the whole thing is still in flux.
--
Philippe.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-06-30 13:05 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-30 9:12 [Xenomai-help] Xenomai 2.5.6 with Valgrind ? VEYSSIERE Nicolas
2011-06-30 9:33 ` Philippe Gerum
2011-06-30 10:13 ` VEYSSIERE Nicolas
2011-06-30 10:46 ` Gilles Chanteperdrix
2011-06-30 11:03 ` varname
2011-06-30 13:05 ` Philippe Gerum
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.