This is the mail archive of the
mailing list for the Cygwin project.
RE: Cygwin 1.1.0 gdb troubles
- To: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
- Subject: RE: Cygwin 1.1.0 gdb troubles
- From: Heribert Dahms <heribert_dahms at icon-gmbh dot de>
- Date: Tue, 18 Apr 2000 23:08:35 +0200
but how can I get then the proper Unix behavior
for a program foo writing it's getpid() to foo.id:
gdb foo `cat foo.id`
without manually looking up WINPID?
Bye, Heribert (email@example.com)
> -----Original Message-----
> From: Chris Faylor [SMTP:firstname.lastname@example.org]
> Sent: Tuesday, April 18, 2000 21:29
> To: email@example.com
> Subject: Re: Cygwin 1.1.0 gdb troubles
> On Tue, Apr 18, 2000 at 04:45:45PM +1000, Boyd Adamson wrote:
> [Heribert] [snip]
> >Actually, yes, I am able to attach to a running process, although I
> have to
> >use the process ID that the Windows Task Manager gives, not the pid
> >bash gives for a background job. I saw this particular behavior in
> B20 also.
> I.e., it's working as designed. gdb works on more than just cygwin
> Want to unsubscribe from this list?
> Send a message to firstname.lastname@example.org
Want to unsubscribe from this list?
Send a message to email@example.com