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.
PS.
I was going to write my own memcpy function ... but that seems kind of a
poor solution ...
Robert D. Findlay
Senior Software Engineer
FC software Inc.
Tel: (905)659-0512
email: [EMAIL PROTECTED] Web: www.netcom.ca/~fcsoft
--- [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/
