Re: [PATCH 0/6] Protect fork() against dll- and exe-updates.

On 03/30/2016 11:53 AM, Michael Haubenwallner wrote: > Hi, > > this is the updated and split series of patches to use hardlinks > for creating the child process by fork(), in reply to > https://cygwin.com/ml/cygwin-developers/2016-01/msg2.html > https://cygwin.com/ml/cygwin-developers/2016-0

Re: [PATCH] Add minidump write utility

May I recommend setting MiniDumpWithHandleData | MiniDumpWithFullMemoryInfo | MiniDumpWithThreadInfo | MiniDumpWithFullAuxiliaryState | MiniDumpIgnoreInaccessibleMemory | MiniDumpWithTokenInformation | MiniDumpWithModuleHeaders | MiniDumpWithIndirectlyReferencedMemory by default? On 02/07/201

Re: New modes for cygpath that terminate path with null byte, nothing

On 8/14/12 10:02 PM, Christopher Faylor wrote: > On Tue, Aug 14, 2012 at 02:49:17PM -0700, Daniel Colascione wrote: >> On 7/27/2012 2:32 AM, Corinna Vinschen wrote: >>> There's just the problem of the copyright assignment. If you want to >>> provide a non-obvious

Re: New modes for cygpath that terminate path with null byte, nothing

lars of the assignment off-list somewhere? Thanks, Daniel Colascione signature.asc Description: OpenPGP digital signature

New modes for cygpath that terminate path with null byte, nothing

I wrote this patch because I often write this: $ cygpath -aw foo > /dev/clipboard Today, cygpath always appends a newline to the information in the clipboard, which is annoying when trying to paste into a program that interprets newlines specially. This patch implements two new options: -0/--null

Re: [PATCH] Add pthread_sigqueue(3)

On 1/2/12 9:59 AM, Christopher Faylor wrote: > On Sun, Jan 01, 2012 at 12:59:00PM -0600, Yaakov (Cygwin/X) wrote: > I guess this can go in since I already "implemented" sigqueue but > SI_QUEUE isn't actually fully functional. Cygwin doesn't queue signals > and I don't believe it handles the sigval

Re: Add support for creating native windows symlinks

On 12/19/11 11:31 AM, Russell Davis wrote: >> I don't think it's the right approach to let Cygwin create symlinks >> which are only partially usable in the POSIX environment... > > Huh? I think you're not fully understanding my suggested approach. As > I pointed out in my previous message, it shou

Re: Add support for creating native windows symlinks

or security reasons. (This behavior can be changed by using the in-box fsutil program.) I agree that using Windows symlinks to implement symlink(2) is a bad idea. > I think the better approach here is to have an ln-like utility that > creates Windows symlinks, as proposed by Daniel Colas

Re: Problems with: Improvements to fork handling (2/5)

On 5/28/11 7:35 PM, Ryan Johnson wrote: > On 28/05/2011 8:23 PM, Christopher Faylor wrote: >> On Sat, May 28, 2011 at 06:40:30PM -0400, Ryan Johnson wrote: >>> On 28/05/2011 4:50 PM, Christopher Faylor wrote: On Wed, May 11, 2011 at 02:31:37PM -0400, Ryan Johnson wrote: > This patch has th

RE: [PATCH] fix build warnings for functions without return value

> From: cygwin-patches-ow...@cygwin.com [mailto:cygwin-patches- > > I don't see why this is needed. Cygwin uses -Werror by default so, if gcc 4.3.4 > emitted warnings we wouldn't be able to build a release or make a snapshot. It's because Cygwin uses -Werror that I had to patch the source. I'm co

[PATCH] fix build warnings for functions without return value

Stop warnings about function not returning a value; the value is meaningless anyway, but the compiler can't know that. Index: cygwin-1.7.5-1/winsup/cygwin/fhandler_tty.cc === --- cygwin-1.7.5-1.orig/winsup/cygwin/fhandler_tty.cc +++ cy