Re: gdb/1233: gdb causes 'abort' signal when debugging cvs

[Daniel Jacobowitz <drow at mvista dot com>]

The following reply was made to PR gdb/1233; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: esp@pyroshells.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1233: gdb causes 'abort' signal when debugging cvs
Date: Wed, 4 Jun 2003 21:52:59 -0400

 Yes, Solaris doesn't give us enough control to follow forks properly. 
 Well, maybe it does, I'm not terribly familiar with Solaris procfs. 
 But I know that GDB doesn't support this on Solaris.
 
 On Wed, Jun 04, 2003 at 02:28:00AM -0000, esp@pyroshells.com wrote:
 > The following reply was made to PR gdb/1233; it has been noted by GNATS.
 > 
 > From: <esp@pyroshells.com>
 > To: <gdb-gnats@sources.redhat.com>, <nobody@sources.redhat.com>
 > Cc:  
 > Subject: Re: gdb/1233: gdb causes 'abort' signal when debugging cvs
 > Date: Tue, 3 Jun 2003 19:13:59 -0700 (PDT)
 > 
 >  > Thank you very much for your problem report.
 >  > It has the internal identification `gdb/1233'.
 >  > The individual assigned to look at your
 >  > report is: unassigned.
 >  >
 >  >>Category:       gdb
 >  >>Responsible:    unassigned
 >  >>Synopsis:       gdb causes 'abort' signal when debugging cvs
 >  >>Arrival-Date:   Wed Jun 04 01:38:01 UTC 2003
 >  
 >  I hope this is a real person I'm getting whilst responding to this, but I
 >  figured out what was going on...
 >  
 >  it looks like the signal is caused by following a fork into parent code,
 >  whilst a child is running. 'set fork-follow-mode child' doesn't do squat,
 >  nor 'set fork-follow-mode parent'. very irritating, I have to start
 >  another version of gdb in another window.
 >  
 >  Argh.
 >  
 >  
 >  Ed
 >  
 >  
 > 
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer