[Xenomai] Fwd: undefined symbol __wrap_malloc in 3.0.4

-- Forwarded message -- From: George Broz <broz...@gmail.com> Date: 24 August 2017 at 09:13 Subject: Re: [Xenomai] undefined symbol __wrap_malloc in 3.0.4 To: Henning Schild <henning.sch...@siemens.com> On 24 August 2017 at 08:50, Henning Schild <henning.sch...@sie

[Xenomai] undefined symbol __wrap_malloc in 3.0.4

ol message on startup. Can someone please tell me how I can build the application to now find these wrappers? Does it require a Xenomai kernel configuration option to be selected as well? Thanks in advance! --George Broz Moog Industrial Group ___ Xenomai ma

Re: [Xenomai] select() unblocks when no data to read()

On 13 July 2017 at 09:26, George Broz <broz...@gmail.com> wrote: > Hi - > > I'm using the UDD driver on Xenomai 3.0.4 / Linux 3.18.20 on an ARM SoC. > > I use select() to block on read events. The problem is select() unblocks > twice in response to one interrupt event

[Xenomai] select() unblocks when no data to read()

RTDM select() handling? Is there a patch or additional debug someone could suggest? Any input greatly appreciated. Regards, --George Broz Moog Industrial Group ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai

[Xenomai] 0-priority task in Cobalt

through the Cobalt skin? What are the calls/arguments needed? Thanks in advance! --George Broz Moog Industrial Group ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai

Re: [Xenomai] behavior of cobalt-wrapped fwrite()

On 27 December 2016 at 11:37, Philippe Gerum <r...@xenomai.org> wrote: > > On 12/27/2016 06:54 PM, George Broz wrote: > > Hello, > > > > I'm running Xenomai 3.0.2, with Linux 3.18.20. I have an application > > that uses the Cobalt (POSIX) API, using several Xen

[Xenomai] behavior of cobalt-wrapped fwrite()

am I expected to use __real_fwrite() in such cases? And then, should I be using __real counterparts for fopen, fread, etc. as well? And what is the litmus test for using the __real_XXX prefixed function calls? Thanks in advance for any advice! --George Broz Moog Ind

[Xenomai] mapping peripherals through /dev/mem on xenomai/cobalt

ds under Cobalt. My question: Is there a way to mmap peripheral memory via /dev/mem under Cobalt or is an RTDM driver required in this scenario? Bonus question: Where in the Xenomai codebase is the EINVAL determination made in this (/dev/mem) case? Thanks in advance for any insights! --Geo

Re: [Xenomai] slackspot

On 23 August 2016 at 10:14, Alex Plits wrote: > Hi, > > Had the same issue (ARMv7/Cobalt/3.0.2), did not find any solution, fail back > to debugging using the SIGDEBUG signaling catching. > > Best Regards, > Alex Plits. > > -Original Message- Thanks. Has anyone

Re: [Xenomai] slackspot

> Lowell Gilbert writes: > >> Lowell Gilbert writes: >> >>> Gilles Chanteperdrix writes: Ok. Could you post an example allowing us to reproduce the issue ? >>> >>> I can. It took me a little longer than I

Re: [Xenomai] rt_heap_alloc priority inversion

-Philippe Gerum r...@xenomai.org wrote: - On 10/25/2013 11:59 PM, George Broz wrote: Hello All, I'm running Linux 2.6.37.6 w/Xenomai 2.6.1, native API on x86 (Atom, SMP, 32-bit). I have two tasks, both running in Xenomai user-space. One is priority=99 and blocks on rt_intr_wait

[Xenomai] rt_heap_alloc priority inversion

in the memory heap services? Thanks in advance! --- George Broz Moog, Inc. Industrial Group ___ Xenomai mailing list Xenomai@xenomai.org http://www.xenomai.org/mailman/listinfo/xenomai

Re: [Xenomai] rt_heap_alloc priority inversion

-Gilles Chanteperdrix gilles.chanteperd...@xenomai.org wrote: - On 10/25/2013 11:59 PM, George Broz wrote: Hello All, I'm running Linux 2.6.37.6 w/Xenomai 2.6.1, native API on x86 (Atom, SMP, 32-bit). Do you observe the same issues with Xenomai latest release? I can't easily

[Xenomai] properties of task at priority 0

0? Thanks in advance! George Broz Moog, Inc. Industrial Group ___ Xenomai mailing list Xenomai@xenomai.org http://www.xenomai.org/mailman/listinfo/xenomai

Re: [Xenomai] properties of task at priority 0

-Philippe Gerum r...@xenomai.org wrote: - On 02/17/2013 10:01 AM, George Broz wrote: Hello All, I'm using a kernel driver for which some calls cause the Xenomai kernel to crash with a message: Xenomai: stuck on nucleus lock.., but only when called from a Xenomai task