Debugging process launching code
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Thunderbird 2.0.0.24 (Macintosh/20100228) Quitting and re-launching the IDE helps, every time. My processes are launched using forkpty, and only one at a time. /Ingemar _______________________________________________ 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... I am mostly a lurker on the Darwin list since I don't feel I can contribute much, but now I feel I must ask for help on this. For several years, I have been working on my own IDE in my spare time. It is a rather different IDE, extremely minimalistic, looks like a simple editor at first glance, but with a lot of parsing and decision making under the hood. Well, I won't try selling it, I have almost given that up, but I will keep developing it for myself and the few fans it has, because it works just the way I want it to. But it has one single bug that annoys any user including myself: The process management occasionally locks up, totally, so I can't start any processes at all from the program. I have tried finding the bug by starting and stopping lots of processes, but whenever I do that the bug doesn't surface at all. But in normal use, it happens, randomly. There can be hours of use with hundreds of process launches, and then it stops working. How would you debug a problem like this? Are there pitfalls and limitations in process launching that I ought to know about? When will the OS just refuse to fork a process? This email sent to site_archiver@lists.apple.com
participants (1)
-
Ingemar Ragnemalm