Either:

		a) run the app normally , the attach to it after it has forked.
		   ie. 'gdb <progname> <pid>'

		b) comment out the fork() (or daemon()) call :)

			David

 D.K.Brownlee@city.ac.uk (MIME) +44 171 477 8186  {post,host}master  (abs)
Network Analyst, UCS, City University, Northampton Square, London EC1V 0HB.
 <<< Monochrome - Largest UK Internet BBS - try telnet mono.city.ac.uk >>>

On Tue, 18 Jul 1995, Gerald C. Simmons wrote:

> Now I'm in unfamiliar territory! I'm trying to debug a pop Daemon using gdb.
> Just how do I do that. The program starts, binds itself to the appropriate
> socket, fork()'s itself into the background, and "exits normally." Obviously I
> need the debugger to follow the forked process. How do I do that?
> 
> Gerry Simmons
> simmons@darykon.wa.com
> 
> 
>