X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=L7Fh2iMl1UJrNS5J
	j6+xEnWh5gIzX/oiI4Rw8LNuaP+udlOeZHZZ1R7u0Pu5WQoHZqkXICAtNIUFesnG
	0UyDdOhVIeXjrhUr6o5W60x88FZv+9HdodM9rQ1RTaBxAccITYPwtKBoam28Gndx
	rWXFlvVtvFo4xJ7g7A8uz9mb7Rg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=PyYGGKUqENsBKINTFSxDZM
	Ac4JA=; b=M2r9qOQHLXEUHw5TTglGdEn7IxBToGw05JsM8zKNqCqClHwYdbbAhx
	8Jh5a+DnLcKj951cAa1YLfbJnXmdEDrJ47MGZrCb/0iqZtJm/1muK3sGJzGEknNV
	FQ8UZQ7CPPhKV+jZTOBptUVW/Z6pCOT2wIoxZ2WtSxL9eN1BFSGUM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=packaging, attaching, Walsh, walsh
X-HELO: out2-smtp.messagingengine.com
X-ME-Sender: <xms:agjjWr7mitG-bX3uugjdstk9iKuWm0ppC5WHUgj11viOt0jSkN5xmw>
Subject: Re: odd behavior(bug?) during run of setup
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <5AE28B9C DOT 9070209 AT tlinx DOT org>
Cc: L A Walsh <cygwin AT tlinx DOT org>
Reply-To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID: <a5b71425-e865-8cf7-7233-bd0ca7801b53@dronecode.org.uk>
Date: Fri, 27 Apr 2018 12:24:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5AE28B9C.9070209@tlinx.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 27/04/2018 03:31, L A Walsh wrote:
> When running setup -- a few time have gotten an error saying that it
> couldn't create /llvm-objdump.exe.stackdump

Thanks for reporting this.

Giving the actual error you see, rather than "an error" would be helpful.

Attaching the setup log file would also be helpful.

> (setup-x86-64-2.891)
> 
> I looked, and there is no such file in the root dir, so I traced it
> with process monitor and first saw it try to
> CreateFile C:\llvm-objdump.exe.stackdump (Name not found)
> Then
> CreateFile C: ACCESS DENIED.
> 
> Since that's the only ref to llvm-objdump.exe.stackdump and
> the only place with an access denied right after it, I suspect
> that's where the error is coming from.
> 
> So for some reason it seems to be trying to create a
> stackdump, but first it's trying to create the hard drive
> (C:).
> 
> Weird.
> 
> Told it to ignore -- and setup went on an finish w/no further probs.
> 
> So maybe there was a stackdump during setup and it
> tried to create the dir that is topmost?

This looks like a packaging hiccup with clang:

https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fcompiler-rt%2Fcompiler-rt-5.0.1-1&grep=llvm-objdump.exe.stackdump

I think you can safely ignore this error, for the moment.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple