On Monday, September 9, 2002, at 12:23 AM, devdrvr.net Multi-Platform SW wrote: #0 0x9001bc0c in kill () #1 0x9005d5cc in abort () #2 0x90006ac4 in _lu_fork_child () #3 0x9000d410 in _lu_running () #4 0x9008a560 in getserv () #5 0x001ae3f0 in serv_name_lookup (port=49229, proto=PT_NONE) at resolv.c:236 Using libpcap-0.7.1's pcap_read() in my code I sometimes get this abort later up the stack. Now I can't get it to happen at all (after trying sans windowing system and going back to Aqua) and I forgot the exact mach port abort message that got spit out at me. resolv.c is not mine. It's not really a Mach error. The dyld subsystem failed [to do on-the-fly symbol resolution] in a place where it never should. So, aborting was its only option. The question is: Why? It could be a reentrancy problem. You aren't calling this from a signal handler, are you? Anything that does these kinds of library calls are not safe from a signal handler. But without information about what stack frames 6->N are, there is no good way to tell from here. --Jim _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.