site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Dec 1, 2005, at 10:08 PM, Julian Mayer wrote: - its prebound, incorrectly. - its been stomped by a memory smasher. You might turn off prebinding and see if that fixes the issue. Chris _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... IOIteratorNext does not call CFRelease at + 0x10, it calls _io_iterator_next by way of a dyld_stub, which loads a function pointer and jumps to it. There are only two reasonable ways that dyld's function pointer could be wrong. My bet, from having witnessed this happen before, is the first. it is still not clear to me why the binary in question crashes on one machine and runs properly on all other...is there a real problem and the prebinding problem only accounts for an incorrect crash log, or is prebinding completely responsible for the problem? if so, what do i have to do to remedy this problem? does this also mean that the rest of the crash log is also wrong? You may find a difference between 10.3.9 vs 10.4.x. Also, if prebinding is redone by an installer, the problem may (or may not) be magically fixed (or magically broken). In one case -- in a dylib I dynamically loaded using NSAddImage -- not only did I have to disable prebinding, I had to set the "bind everything at load time" flag. It "just worked" on 10.4.x, but on 10.3.9, it would bind incorrectly at runtime -- but not on all 10.3.9 systems, just some of them... This email sent to site_archiver@lists.apple.com