How should I report a critical type of Cygwin bug?

[Corinna Vinschen]

On Feb 26 17:00, Shaddy Baddah wrote:
> Hi,
> 
> Risking the wrath that I should just report the bug, I would like to
> just get some advice on how to go about it.
> 
> I'm encountering a problem with a rather new Cygwin package/feature that
> if reproducible, has serious consequence on the hosting Windows
> platform.
> 
> My concern is that if I list the steps here, readers will blindly try
> this (rather easily performed) action and break their computer.

Cygwin is a user space DLL.  It cannot break the OS, unless you do
something really terrible like rm -rf in /cygdrive/c with admin rights,
but you can do the same with CMD.  And we also don't access or try to
write UEFI variables, usually.  Hmm, /proc/sys, maybe?

> Should I just whack on a disclaimer and report it?

Yes, please.  Please see http://cygwin.com/problems.html.  A simple
testcase would be cool.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20140226/a3c65839/attachment.sig>