On Sat, Mar 15, 2003 at 09:23:50PM -0800, S Yuval wrote: > I've been trying to trace through a simple TCP wrote I wrote based on > explanations in Richard Stevens' "Unix Network Programming". The program > behaves normally, but I can't trace into the forked process. Anjuta simply > ignores its existance and KDevelop crashes. Any suggestions?
Interesting example. It would possibly be easier to rewrite it as two seperate programs, thus avoiding the need to fork. If you do want to trace this, try using gdb directly instead; it should be able to trace both parent and child processes. And I'd recommend lowering your process limits (see ulimit) while playing with fork(), just in case you accidentally create yourself a fork bomb (a program that keeps forking without the processes exiting). Also, this is probably the wrong forum for this type of question. Maybe try posting to anjuta or kdevelop mailing lists, then they might also look to try to fix the bugs not letting you do what you want. HTH, Pete -- Pete Ryland http://pdr.cx/
pgpST0CUplUm8.pgp
Description: PGP signature
