Hi Gilles and Dmitry, I actually prefer Gilles proposal to add the fault_vm() function after calling a forking function. Dmitry's idea with a different context and inter process communication will surely work but it makes the code less transparent as when using the fault_vm() function. Are there situations where the fault_vm() could fail or is this fine in all situations?
Regards Mathias > M. Koehrer wrote: > > Good morning everybody, > > > > here are some more news concerning the Xenomai crash issue. > > 1) I have tried to enable the CONFIG_DEBUG_SPINLOCK and > CONFIG_DEBUG_SPINLOCK_SLEEP > > kernel config parameters. But I did not get any messages before the kernel > freezes. > > > > 2) I have tried to link a static application (using -lstatic). When I > pass > > the -L/usr/lib/nptl option to force the linker to use the nptl libs, the > effect is the same. > > Well, I have now a static binary that freezes the system. > > I can mails you the binary file (about 280kByte bz2 file) if you like. > > I think this file is too large to be posted to the list. > > > > One additional question comes in my mind: > > As I learned from all that things that are related to the issue, it seems > to be fairly > > critical to fork out of a real time task or to create new processes out of > it. > > In absence of a better solution, I would recommend to use the "fault_vm" > function after each fork. > -- 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
