Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A0AAE94.2594EBDE@redhat.com> Date: Thu, 09 Nov 2000 15:03:00 +0100 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin Subject: Re: Debugging child process References: <001001c04a51$3bd560e0$21c9ca95 AT mow DOT siemens DOT ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Andrej Borsenkow wrote: > > I need to debug a process immediately after fork. IIRC gdb under cygwin cannot > continue debugging across forks (is it correct?) I've tried to add sigpause() > to be able to attach to child, but somehow it does not work. Child stops, I > can attach and set breakpoint, but cont'ing does not works (I say cont and > send signal from shell but child never seems to hit breakpoint). > > Any idea? Did you attach to the correct process? I'm asking because you have to care for the PID. GDB needs the WINPID as argument, not the Cygwin PID. Just a hint, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com Red Hat, Inc. mailto:vinschen AT redhat DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com