Yes, problems with ffcall and mprotect are becoming more common as newer kernels and processors implement more strict memory checking. I imagine this problem has something to do with the effective user or something...
Anyway, you could file a bug report for ffcall: http://sourceforge.net/tracker/?atid=101355&group_id=1355&func=browse but they have not been very quick in working on the fundamental problem that ffcall has with this, so I don't expect it will get fixed anytime soon. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manuel Guesdon Sent: Monday, April 16, 2007 7:34 AM To: gnustep-dev@gnu.org Subject: Re[2]: su, FFCall & crash On Sun, 15 Apr 2007 18:52:50 +0200 (CEST) Manuel Guesdon <[EMAIL PROTECTED]> wrote: >| I finally suspect no-exec proc flag or somethning like this as ffcall self tests doesn't work under 'su'..... For the records, after 3 days of investigations, I found the problem: One should do a su before ffcall 1.10 configure In config.h, you should have /lists.gnu.org/mailman/listinfo/gnustep-dev _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
