At 01:41 PM 27-07-99 -0400, Robert Findlay wrote:
>I had a working module which included 2 instances of "memcpy".
>
>All appeared to work fine.
>
>I added a new function to my RT module which also called "memcpy".
>Everything compiles fine but when the module is loaded it complains that it
>can't find "memcpy". It gets weirder ... if I comment out my original
>working memcpy instances I simply can't get my new module to load ...
>unless I comment out the "memcpy" line in that new function (and yes it is
>spelled correctly). I even tried creating a "my_memcpy" function which
>called "memcpy" ... no way. There seems to be something magic about the
>position of those original "memcpy" statements in the original code which
>works ...
>
>Can anyone shed some light on what is wrong? Is memcpy not a good function
>to be using inside an RT module? Is there something I should be doing to
>tell the RT module about memcpy?
>
>Any help would be appreciated.
In general I avoid linking with any librairies (static or shared). Code in
librairies can and may assume you're running in user space. Functions like
malloc free memcpy memset etc can be implemented in a separate module that
acts like a library. Particular attention must be given to malloc and free
if more than one context will use them.
Regards,
Pierre Cloutier
_______________________________________________________
Pierre Cloutier
Tel: (450)-659-9186
Fax: (450)-659-0014
POSEIDON CONTROLS INC
_______________________________________________________
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
