June 2007 - Darwin-dev - lists.apple.com

Re: Where can I find a comprehensive manual for the openfirmware of Mac?
by Garth Cummings 25 Jun '07

25 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

A question of Rosetta.
by Calvin (Yu-Hui) Liu 25 Jun '07

25 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.4 (Windows/20070604) Hi, there, Since Rosetta is a translation process that allows us to use PowerPC-based apps on Intel-based Mac and it's not a simulator of PowerPC, then I suppose it's a translator of machine instructions. If so, why Java applets in a web browser that Rosetta can run translated will not be able to loaded? (Suppose we already have correct JVM installed.) And how about flash plugins? Thanks. Calvin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Where can I find a comprehensive manual for the openfirmware of Mac?
by Calvin (Yu-Hui) Liu 24 Jun '07

24 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.4 (Windows/20070604) As subject. I tried to google it but openfirmware.org pointed me back to Apple, which has not such information. Thanks a lot! - Calvin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

sysctlbyname( "hw.availcpu" ) fails
by Steve Checkoway 23 Jun '07

23 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com #include <sys/types.h> #include <sys/sysctl.h> #include <stdio.h> int main() { int mib[2] = { CTL_HW, HW_AVAILCPU }; int cpus; size_t size = sizeof( cpus ); if( sysctl(mib, 2, &cpus, &size, NULL, 0) == -1 ) perror( "sysctl" ); else printf( "sysctl: %d\n", cpus ); size = sizeof( cpus ); if( sysctlbyname("hw.availcpu", &cpus, &size, NULL, 0) == -1 ) perror( "sysctlbyname" ); else printf( "sysctlbyname: %d\n", cpus ); size = 2; if( sysctlnametomib("hw.availcpu", mib, &size) == -1 ) perror( "sysctlnametomib" ); size = sizeof( cpus ); if( sysctl(mib, 2, &cpus, &size, NULL, 0) ) perror( "sysctl2" ); else printf( "sysctl2: %d\n", cpus ); return 0; } When I run it, I get: $ ./a.out sysctl: 2 sysctlbyname: No such file or directory sysctlnametomib: No such file or directory sysctl2: 2 $ sysctl hw.availcpu hw.activecpu hw.availcpu = 2 hw.activecpu: 2 -- Steve Checkoway _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com When I try to use sysctlbyname with "hw.availcpu", I get an error but when I use { CTL_HW, HW_AVAILCPU } with sysctl, it succeeds. Here is my test case: What is the difference between activecpu and availcpu, e.g., why does one have an equal sign and the other a colon? A similar issue I found in the list archives was <http:// lists.apple.com/archives/darwin-development/2003/Aug/msg00256.html>. Just to be clear about this, I only want the information for my own debugging purposes. Absolutely nothing in the code makes any decisions based on the number of cpus. smime.p7s

1 0

Re: size of "disk cache"
by Uli Kusterer 23 Jun '07

23 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Cheers, -- M. Uli Kusterer http://www.zathras.de _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On 23.06.2007, at 08:52, Calvin (Yu-Hui) Liu wrote: I don't have enough experience on Mac so far. I'm not quite sure if the "Disk Cache" here refers to "swap partition" as Linux. In my experience on Linux, I was told to use as same size as the physical memory - 1GB swap for 1GB memory. "32K for every MB" - it seems to be too small... What do you think? This info is for Mac OS 9 and earlier. OS 9 isn't a Linux, it's a pre-Darwin MacOS (what you get when you run a "classic" application on a PowerPC Mac). So, this isn't really on topic for this mailing list, and you may wanna look for another venue to ask your question. That said, I'll try to provide an answer: The equivalent to Linux's "swap" partition would be "Virtual Memory", which is set up separately, and generally is your physical amount of RAM +x. Since OS 9 is a rather "old" generation of OS design, it didn't remap memory the way Linux did it either. I think the maximum VM amount was 2x amount of RAM. Disk Cache is usually built into hard disks themselves these days, though OS X does some buffering itself. Anyway, unless you're into retro computing or have customers or users in educational or DTP settings that haven't been able to move to OS X, you'll just want to ignore any "pre-OS X" information. Classic MacOS is a completely different operating system than Mac OS X. Their only commonalities are that they support a number of the same protocols and file formats, and that some (mostly user-level) applications were ported over. Apple is no longer selling Macs able to run OS 9 or earlier, nor is it selling OS 9 itself. It's a dead product. Oh yeah: OS X doesn't have a swap partition by default. It just uses the boot volume for swap space. Though you can find instructions on the web how to screw with the config files to get a dedicated swap partition. But that stuff isn't widely used, and not supported by Apple (at least for "regular" Mac OS X -- not sure about Mac OS X Server, and I guess there's some Darwin users who do a separate swap partition, too). This email sent to site_archiver(a)lists.apple.com

1 0

size of "disk cache"
by Calvin (Yu-Hui) Liu 23 Jun '07

23 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.4 (Windows/20070604) Hi, there, I'm reading an article from Apple "service training". It says "Disk Cache... In versions of the OS previous to X, the amount of cache is set in the Memory control panel. However, it's best to leave the setting at the defualt. Too much or too little cache can adversely affect performance. The optimum setting for disk cache is 32K for every MB of installed RAM." I don't have enough experience on Mac so far. I'm not quite sure if the "Disk Cache" here refers to "swap partition" as Linux. In my experience on Linux, I was told to use as same size as the physical memory - 1GB swap for 1GB memory. "32K for every MB" - it seems to be too small... What do you think? Thanks. - Calvin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: SIGPIPE and SIG_IGN
by Terry Lambert 19 Jun '07

19 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Near the end of signal.h there is this: /* * signals delivered on a per-thread basis. */ #define threadmask (sigmask(SIGILL)|sigmask(SIGTRAP)|\ sigmask(SIGIOT)|sigmask(SIGEMT)|\ sigmask(SIGFPE)|sigmask(SIGBUS)|\ sigmask(SIGSEGV)|sigmask(SIGSYS)|\ sigmask(SIGPIPE)) Is this not true? - Neither of these happen for a SIGPIPE. - - sigprocmask() But I *HIGHLY* recommend the tutorial in the O'Reilly pthreads book. -- Anything more *REALLY* needs a cut-down test case and a bug filed. -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On Jun 18, 2007, at 6:10 PM, Glenn Anderson wrote: At 5:30 pm -0700 18/6/2007, Terry Lambert wrote: This also means that the signal will not get sent if you are ignoring it, and it's in your process signal mask (sigaction() is generally preferred to calling signal(), but either should work). It is has been my experience that if you want to ignore SIGPIPE, you have to ignore it on every thread that could trigger it (ie: call signal(SIGPIPE, SIG_IGN) on every thread that writes to sockets that could close), you can't just ignore it for the whole process. I pretty much rewrote all of the signal handling code in the kernel for UNIX conformance for Leopard, so I'm rather familiar with the code here for both Tiger and Leopard. 8-). The threadmask is only consulted when threadsignal() is called, which only happens in catch_exception_raise(), and in proc_exit() or vproc_exit() when the process is exiting and may need to signal a specific thread in a sigwait(). The catch_exception_raise() only happens when you raise an exception on an exception port as a result of sending a Mach message, usually from user space, usually as a result of a C++ exception being thrown. There are two levels of masking, one for threads, and one for the process. If you set the process mask, the signal is not delivers to the process, period. You can also block the delivery via sigblock() (but it gets pended, so when it's unblocked, it will get delivered). If the signal is masked on a thread but not on a process, then it will get delivered to any thread in the process except the thread(s) that masked it. This happens in the BSD AST handling code when any given thread that does not have the signal masked runs up to the user/kernel boundary, which triggers the trampoline code to run in user space to fire the signal handler on that thread (it does this by returning to an address offset from the intended system call return address). The user space signal handler fires, and, on completion calls __sigreturn() to throw it back into the kernel to complete the call that you were trampolined from, and return to user space. The main issue that people tend to miss when they mix threads and signals is that all of the standard POSIX (and BSD) interfaces are process-wide _and MUST be_, since they predate the concept of pthreads. The only way to deal with threads issues directly is to use the threads APIs AFTER using the standard historical APIs; specifically, you want to mask the signals using the API: And you want to deal with the thread masking to mask it for all threads via pthread_sigmask() on a thread-by-thread basis; there's sample code that gives a (really: don't use it directly) abbreviated example here: <http://www.opengroup.org/onlinepubs/009695399/functions/pthread_sigmask.html > >From the description, without a cut down test case and a bug filing including the test case, we can't really help you further, other than to point you at documentation. What you have described seeing should not be happening, (and doesn't according standards-based testing). What is most likely happening is that you have a library or a class, template, etc., which is either creating a thread behind your back, or is messing around with the signal mask for the thread and/or process. Note that the standard template library *will* create threads on your behalf when you utilize some templates, so that could be your culprit. In general, the most appropriate approach is to designate a signal thread by storing it's pointer off, and if you get the signal on a thread other than the signal thread (pthread_self() doesn't match the catcher thread's ID), then re-throw it to the correct thread using pthread_kill(). In the case that you are attempting to ignore a signal entirely, you need to make sure no one else is messing with your process/thread signal mask behind your back. This email sent to site_archiver(a)lists.apple.com

1 0

Re: SIGPIPE and SIG_IGN
by Glenn Anderson 19 Jun '07

19 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com /* * signals delivered on a per-thread basis. */ #define threadmask (sigmask(SIGILL)|sigmask(SIGTRAP)|\ sigmask(SIGIOT)|sigmask(SIGEMT)|\ sigmask(SIGFPE)|sigmask(SIGBUS)|\ sigmask(SIGSEGV)|sigmask(SIGSYS)|\ sigmask(SIGPIPE))

1 0

Re: SIGPIPE and SIG_IGN
by Terry Lambert 19 Jun '07

19 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Hello, all ... // set up our signal handlers signal( SIGINT, signal_handler ); signal( SIGTERM, signal_handler ); #ifndef WIN32 signal( SIGPIPE, SIG_IGN ); #endif -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On Jun 18, 2007, at 4:25 PM, Glenn Anderson wrote: At 4:09 pm -0700 18/6/2007, jmzorko(a)mac.com wrote: In my adventures of making our app also work on Mac OSX (10.4.9, Intel and PPC), i've discovered that I occasionally get SIGPIPE signals. This would be fine, except that I specifically ignore them like this: ... so my question is: why do I still get SIGPIPE signals, which make my program go boom? What else do I need to do such that SIGPIPE is actually ignored? I don't _always_ get them, but they come up often enough to be a problem. SIGPIPE is a per-thread signal, so you need to do signal( SIGPIPE, SIG_IGN ) on every thread dealing with the relevant sockets. Alternatively you can use setsockopt() with SOL_SOCKET and SO_NOSIGPIPE to turn off SIGPIPE for a socket. Actually, SIGPIPE is raised via psignal in all but one case; that case is a EXC_UNIX_BAD_PIPE exception being raised (which we never raise; I should delete this case entry from the switch statement at some point, I guess). So this is all psignal() generated, with a flavor argument of 0, which means it's per process, and the thread that gets signalled will be whatever thread is the current thread at the front of the list of active threads for the process. This also means that the signal will not get sent if you are ignoring it, and it's in your process signal mask (sigaction() is generally preferred to calling signal(), but either should work). Unless there's a library mucking with signals behind your back, you'd need to provide a reproducible case of getting the signal in a cut- down program in a bug report for us to help you out with your problem. If you are using per-thread signals, you have to program a very specific way for this to work (see the O'Reilly pthreads book for details), since there's a lot of "behaviour is undefined" type behaviours when mixing thread signal masks and process masks. It should also be noted that when a signal is raised, it may not end up interrupting the operation in progress, since it may have run to completion by the time you get back up to the kernel/user boundary to hit the trampoline (we are like True64 UNIX in this regard, which is also Mach-based and also uses Mach ASTs for signal delivery). So if the signal happens before you ignore it, there's a small window in which it's possible for the signal to hit you. If you bug report this, make sure that you make it clear as to whether this is a pipe, a socket, a named pipe, or a UNIX domain socket that's triggering it. This email sent to site_archiver(a)lists.apple.com

1 0

Re: SIGPIPE and SIG_IGN
by Glenn Anderson 18 Jun '07

18 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Hello, all ... // set up our signal handlers signal( SIGINT, signal_handler ); signal( SIGTERM, signal_handler ); #ifndef WIN32 signal( SIGPIPE, SIG_IGN ); #endif Glenn. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… At 4:09 pm -0700 18/6/2007, jmzorko(a)mac.com wrote: In my adventures of making our app also work on Mac OSX (10.4.9, Intel and PPC), i've discovered that I occasionally get SIGPIPE signals. This would be fine, except that I specifically ignore them like this: ... so my question is: why do I still get SIGPIPE signals, which make my program go boom? What else do I need to do such that SIGPIPE is actually ignored? I don't _always_ get them, but they come up often enough to be a problem. SIGPIPE is a per-thread signal, so you need to do signal( SIGPIPE, SIG_IGN ) on every thread dealing with the relevant sockets. Alternatively you can use setsockopt() with SOL_SOCKET and SO_NOSIGPIPE to turn off SIGPIPE for a socket. This email sent to site_archiver(a)lists.apple.com

1 0