public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-developers@cygwin.com
Subject: Re: cygwin_create_path causes null pointer crashes
Date: Wed, 14 Dec 2016 20:25:00 -0000	[thread overview]
Message-ID: <018dd75a-b8ec-27fe-a056-d4dd5191b54f@towo.net> (raw)
In-Reply-To: <20161213115648.GA17377@calimero.vinschen.de>

Am 13.12.2016 um 12:56 schrieb Corinna Vinschen:
> On Dec 12 20:28, Thomas Wolff wrote:
>> Hi Corinna,
>>
>> Am 11.12.2016 um 12:08 schrieb Corinna Vinschen:
>>> Hi Thomas,
>>>
>>> On Dec 10 03:03, Thomas Wolff wrote:
>>>> cygwin_create_path is supposed to call malloc itself,
>>>> however, it occasionally returns with null and errno == ENOSPC,
>>>> if it's provided with a network path, e.g.
>>>> cygwin_create_path(CCP_POSIX_TO_WIN_W, "/cygdrive/s/.config/mintty")
>>>> returns null in ~ 3 of 1000 cases, where /cygdrive/s exists but
>>>> /cygdrive/s/.config does not
>>> Did you try to debug and fix the issue?  This is the developer's mailing
>>> list after all...
>> I can contribute some initial analysis:
>> Cloning cygwin_create_path from cygwin/path.cc with these essentials:
>>    ssize_t size = cygwin_conv_path (what, from, NULL, 0);
>>    // checking size, calling malloc
>>    if (cygwin_conv_path (what, from, to, size) == -1)
> Cloning?  Why didn't you just debug with GDB and/or strace?
Well, one reason is that I had to manipulate the value of size between 
the two calls ...

>> ...
> A simple strace shows that there's a really ugly problem with network shares:
>
> ...
> Anyway, we can't fix Windows, but we can workaround its problems, which
> is what Cygwin does, so I applied a patch.
Great, this works, thanks.

Thomas

      reply	other threads:[~2016-12-14 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-10  2:03 Thomas Wolff
2016-12-11 11:08 ` Corinna Vinschen
2016-12-12 19:28   ` Thomas Wolff
2016-12-13 11:57     ` Corinna Vinschen
2016-12-14 20:25       ` Thomas Wolff [this message]

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=018dd75a-b8ec-27fe-a056-d4dd5191b54f@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-developers@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).