On Wed, 15 Apr 2020 at 03:22, Alec Ari via Emc-developers
<[email protected]> wrote:
>
> Yes, now what do we do about it? I need ideas!
Interesting info in the RTAI code:
* rtai_malloc is used to allocate shared memory from user space.
*
* @param name is an unsigned long identifier;
*
* @param size is the amount of required shared memory;
*
* rtai_malloc is a legacy helper macro, the real job is carried out by a
* call to rt_shm_alloc() with the same name, size and with vmalloc support.
* This function should not be used in newly developed applications. See
* rt_shm_alloc fro more details.
*
* @returns a valid address on succes, on failure: 0 if it was unable to
* allocate any memory, MAP_FAILED if it was possible to allocate the
* required memory but failed to mmap it to user space, in which case the
* allocated memory is freed anyhow.
Whereas LinuxCNC says:
// the check for -1 here is because rtai_malloc (in at least
// rtai 3.6.1, and probably others) has a bug where it
// sometimes returns -1 on error
It seems it isn't a bug, really.
Though it isn't getting me any closer to what is wrong.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
