Hi,
I encountered a strange problem in our iOS app when trying to build for iOS5. Here is what I get in the console before the app crashes:
Jan 26 19:52:41 unknown sandboxd[3643] <Notice>: Topos(3639) deny file-ioctl /private/var/mobile/Applications/ABA9866E-15FA-4416-84E7-5FC45665D339/Documents/export.kml
It seems that some file-ioctl operations that Gambit uses for writing files are disabled in the sandbox environment.
Is there an easy solution to that?
Thank you, Francois Magnan
Afficher les réponses par date
On 2012-01-26, at 8:05 PM, Francois Magnan wrote:
Hi,
I encountered a strange problem in our iOS app when trying to build for iOS5. Here is what I get in the console before the app crashes:
Jan 26 19:52:41 unknown sandboxd[3643] <Notice>: Topos(3639) deny file-ioctl /private/var/mobile/Applications/ABA9866E-15FA-4416-84E7-5FC45665D339/Documents/export.kml
It seems that some file-ioctl operations that Gambit uses for writing files are disabled in the sandbox environment.
Is there an easy solution to that?
The only ioctl that I can think of is one that puts the file descriptor in non-blocking mode (this is done to implement the thread system and allow concurrent I/O operations by different threads). This could be disabled easily to see if that's the cause of the problem. In file lib/os_io.c, comment-out the body of the function set_fd_blocking_mode and add a "return 0;".
Otherwise, build Gambit with --enable-debug and look at the content of the "console" file. The last few lines should indicate what system calls returned a nonzero error code.
Marc
Yes it works! Thank you, Francois
On 2012-01-26, at 22:16, Marc Feeley wrote:
On 2012-01-26, at 8:05 PM, Francois Magnan wrote:
Hi,
I encountered a strange problem in our iOS app when trying to build for iOS5. Here is what I get in the console before the app crashes:
Jan 26 19:52:41 unknown sandboxd[3643] <Notice>: Topos(3639) deny file-ioctl /private/var/mobile/Applications/ABA9866E-15FA-4416-84E7-5FC45665D339/Documents/export.kml
It seems that some file-ioctl operations that Gambit uses for writing files are disabled in the sandbox environment.
Is there an easy solution to that?
The only ioctl that I can think of is one that puts the file descriptor in non-blocking mode (this is done to implement the thread system and allow concurrent I/O operations by different threads). This could be disabled easily to see if that's the cause of the problem. In file lib/os_io.c, comment-out the body of the function set_fd_blocking_mode and add a "return 0;".
Otherwise, build Gambit with --enable-debug and look at the content of the "console" file. The last few lines should indicate what system calls returned a nonzero error code.
Marc
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
-
Francois Magnan -
Marc Feeley