*BSD News Article 55596


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!uwm.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!EU.net!peer-news.britain.eu.net!demon!mail2news.demon.co.uk!beckley.demon.co.uk
From: Ian W Taylor <iwta@beckley.demon.co.uk>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Q. on gdb and fork()
Date: Wed, 29 Nov 95 07:50:54 GMT
Organization: Glencarn Ltd.
Lines: 21
Message-ID: <817631454snz@beckley.demon.co.uk>
Reply-To: iwta@beckley.demon.co.uk
X-NNTP-Posting-Host: beckley.demon.co.uk
X-Newsreader: Demon Internet Simple News v1.30

Anyone help me with this problem ?

When stepping through a program using gdb the program fork()s
and then the parent read()s from the child.  GDB sticks with the
parent and the child remains a Zombie.

So the question is how do I get gdb to either swap its attentions
to the child or release the child to run on its own.  I can't 
'attach' to the child 'cos its a zombie, and if I 'detach' the parent
the read() returns zero bytes so the parent craps out taking its 
children with it.

Once I've got the answer to this question the next one will 
probably be how do I get gdb to handle the execv() that the child
does.  Is it just a matter of a new 'file' command.

TIA.
-- 
Regards,
   Ian T.