All,
I run OS X in 64 bit mode (Snow Leopard), and have had no trouble running vw7.6nc in that mode. I successfully installed vw7.7nc, but it turns out I had to have OS X in 32 bit mode else the installer would just crash. However when I switched back to 64 bit mode, 7.7 will not start at all. I see the following output in the Mac Console: 1/19/10 10:11:09 PM [0x0-0x26026].com.cincom.vw7.7[348] VisualWorks(R) 7.7 Non-Commercial Dec 15, 2009 1/19/10 10:11:09 PM [0x0-0x26026].com.cincom.vw7.7[348] src/plat/unxUtil.c:1209 1/19/10 10:11:09 PM [0x0-0x26026].com.cincom.vw7.7[348] Fatal error: setting sys fd owner: Inappropriate ioctl for device 1/19/10 10:11:09 PM com.apple.launchd.peruser.501[165] ([0x0-0x26026].com.cincom.vw7.7[348]) Exited with exit code: 9 If I run the X11 vm in 64 bit mode, everything seems to work just fine. Regards, Todd Edwin King _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Am 20.01.2010 um 04:24 schrieb Todd King: > I run OS X in 64 bit mode (Snow Leopard), and have had no trouble > running vw7.6nc in that mode. This doesn't seem to be related to the VW version. I'm seeing this exact same crash with 7.5 too. The code that seems to cause the crash hasn't changed for a long time (if I don't miss something): src/plat/unxUtil.c:1209 Fatal error: setting sys fd owner: Inappropriate ioctl for device Therefore I would guess there's some incompatibility with 64bit kernel mode. This is a very serious bug, because most Mac Pro machines run in 64 bit kernel mode nowadays. Andre _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
looks like Mac OS X supports the SIOCSPGRP ioctl for sockets, not the F_SETOWN fcntl (which perhaps only works for files?). So someone should try using ioctl(fd, SIOCSPGRP, ... on 64-bit Mac OS and see if it works.
On Wed, Jan 20, 2010 at 4:23 AM, Andre Schnoor <[hidden email]> wrote:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Andre Schnoor
I don't have any experience with 7.5 on the Mac, so I don't know how it behaves on OS X 64 bit mode - I might try it out to see.
But I have been running 7.6 in OS X 64-bit mode since October without any problems what-so-ever. Which is why it is perplexing to me that 7.7 won't work in the same mode (unless I use the X11 VM).
Maybe it has something to do with something simple like the installer installing the wrong VM? -Todd King On Wed, Jan 20, 2010 at 7:23 AM, Andre Schnoor <[hidden email]> wrote:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi all.
Yesterday, I downloaded the 7.7nc version. Like Todd, I'm running 7.6nc since a couple of weeks in my macbook pro with snow leopard on 64 bits mode without any problem. I have the same issue with the last version, too.
Somebody in the list (maybe someone from cincom) know about when we could have a fix for that? (other than run snow leopard in 32 bits mode).
Thanks.
Maxi.
2010/1/20 Todd King <[hidden email]> I don't have any experience with 7.5 on the Mac, so I don't know how it behaves on OS X 64 bit mode - I might try it out to see. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
No, at this point we don't know when could have a fix for
it, as we don't really know what's going on yet. We have two plausible
suggestions - that there is something related to threading, and Eliot's
SIOCSPGRP. We need to follow those up.
At 03:55 PM 2010-01-25, Maximiliano Taborda wrote: Hi all. Yesterday, I downloaded the 7.7nc version. Like Todd, I'm running 7.6nc since a couple of weeks in my macbook pro with snow leopard on 64 bits mode without any problem. I have the same issue with the last version, too. Somebody in the list (maybe someone from cincom) know about when we could have a fix for that? (other than run snow leopard in 32 bits mode). Thanks. Maxi.
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
It would be nice if the user could easily choose whether
to see the children of a given class or not, as is now so common in other
popular systems.
Victor
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
+1 Dave Stevenson[hidden email] From: Victor <[hidden email]> To: [hidden email] Sent: Tue, January 26, 2010 1:07:46 PM Subject: [vwnc] vw7.6nc Hierarchy compressibility It would be nice if the user could easily choose whether to see the children of a given class or not, as is now so common in other popular systems.
Victor
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
+1
Is it possible to remember visibility sets across updates to a tree? As in, if I add things to the tree (by refreshing a parent), it keeps the previous expansion status while it adds the new items? Invariably I find that the status of children of an affected parent gets adjusted. Is it possible to retain this across views in the RB (as you switch in and out of the navigator functions)?
Cheers!
From:
[hidden email] [mailto:[hidden email]] On Behalf Of Dave Stevenson
+1 Dave Stevenson
From: Victor
<[hidden email]> It would be nice if the user could easily choose whether to see the children of a given class or not, as is now so common in other popular systems.
Victor
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |