From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: perl testsuite errors / cygserver not working / apache2 problems (was: Re: [ANNOUNCEMENT] New package: apache2-2.0.54-1 (and subpackages apache2-devel, apache2-manual))
Date: Fri, 08 Jul 2005 17:45:00 -0000 [thread overview]
Message-ID: <20050708174532.GK7507@calimero.vinschen.de> (raw)
In-Reply-To: <20050708173434.GH18981@trixie.casa.cgf.cx>
On Jul 8 13:34, Christopher Faylor wrote:
> On Fri, Jul 08, 2005 at 07:29:17PM +0200, Corinna Vinschen wrote:
> >On Jul 8 17:04, Gerrit P. Haase wrote:
> >> How to debug cygserver?
> >
> >-d option? GDB?
>
> bash-3.00$ -d option? GDB?
> bash: -d: command not found
>
> I think I've mentioned this before... Is cygwin broken?
No, you just got that wrong. It was `diff -d'. If this doesn't
help you can try `perl -d', `cp -d'... or even `cygserver -d'.
Corinna
next prev parent reply other threads:[~2005-07-08 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cygwin.04d501c5775a$d3f75190$e6ec6f83@chimaera>
[not found] ` <42CD8654.2060903@familiehaase.de>
[not found] ` <42CD8745.9080205@familiehaase.de>
[not found] ` <42CD90A0.7080708@familiehaase.de>
[not found] ` <03cf01c58336$cb60ab70$6508a8c0@chimaera>
[not found] ` <42CE3FD7.3050109@familiehaase.de>
[not found] ` <1431.130.240.136.130.1120826827.squirrel@pinus.tt.luth.se>
[not found] ` <42CE95EB.9040803@familiehaase.de>
[not found] ` <20050708172917.GH7507@calimero.vinschen.de>
2005-07-08 17:34 ` Christopher Faylor
2005-07-08 17:45 ` perl testsuite errors / cygserver not working / apache2 problems Gerrit P. Haase
2005-07-08 17:59 ` Corinna Vinschen
2005-07-08 18:02 ` Igor Pechtchanski
2005-07-09 18:34 ` Gerrit P. Haase
2005-07-08 17:45 ` Corinna Vinschen [this message]
2005-07-08 18:04 ` perl testsuite errors / cygserver not working / apache2 problems (was: Re: [ANNOUNCEMENT] New package: apache2-2.0.54-1 (and subpackages apache2-devel, apache2-manual)) One Angry User
2005-07-08 18:17 ` Ed C. Lueless
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050708174532.GK7507@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).