Hi everybody, I have a question that is similar to the one concerning the system() call out of a real time context. I want to create a flexible framework that allows dynamic loading of shared objects during runtime. (The loading itself can of course not work in real time). The main application itself should run for a very long time (a couple of days) and during that long run time I want to load and unload small pieces of code that have to be executed. After loading a .so file I want to hook loaded routines into the (already existing) real time context of my main application. Is it possible that this kind of operation can cause any memory issue similar to that I detected in the 2.6.19 kernel (the system() call out of a real time context)? I ask as the dlopen() call probably extends the valid address range of the current process.
Thanks for any feedback on that question. Regards Mathias -- Mathias Koehrer [EMAIL PROTECTED] Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer, nur 44,85 inkl. DSL- und ISDN-Grundgebühr! http://www.arcor.de/rd/emf-dsl-2 _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
