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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=U4ooSdL9ckQRfk0FvXq9T8W7I8nVgpl9+w1y5BPF3O8IbX6srYS/t
	V03clpj+gZhJpkioVhh8cDM/hG0Eua+wGg5aPPB4pse+802m8+fQNNAMil+pdD63
	cciiscc39hjMRS0Jy8RNgEAOBJZwNoD/4sAz5850PtzwDLiOdovc0U=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=37OHRBdEZzlpbrn0UeHcxFtkgHo=; b=bt9KYYS9egVp9h0fcfYLYqNxamPG
	acITulR8aPXrQQ7+Y3rILw5v11MjZqGZea2Sw2COdwm6rpg5wu6FgtBS1Htm+6Mi
	I4NE/WsJwLSK8tunetv8kefi9NmMqdQv5yI+AjOhRNpog+UdNXlw0KItyjizZLge
	qqYmjxswtVLax2I=
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=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-01-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX185e7eplHChusmcMyaZOlWU
Date: Wed, 8 Jan 2014 01:36:28 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: about cygwin_stackdump()
Message-ID: <20140108063628.GA1732@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAPYQg30BUPUatfdQRe2oHEZpzHBpAQzAX2JHek-RyRB5VtsG2g AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPYQg30BUPUatfdQRe2oHEZpzHBpAQzAX2JHek-RyRB5VtsG2g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Jan 07, 2014 at 11:35:57AM +0900, KIMURA Masaru wrote:
>fopen() stackdump file immediately after cygwin_stackdump() calling in
>signle process fails.
>is this intentional?
>https://github.com/hiyuh/cygwin-stackdump-example

I rewrote your example slightly to make it work with any executable name
by calculating the stackdump name like this:

  char *fname = (char *)malloc(strlen(*__argv) + sizeof (".exe.stackdump"));
  sprintf(fname, "%s.exe.stackdump", *__argv);
  printf("fname = %s\n", fname);

And compiled it as:

gcc -g -DUSE_CYGWIN_STACKDUMP -DUSE_FORK_WAITPID cygwin_stackdump.c -o cygwin_stackdump.exe

That worked fine for me on the most recent Cygwin snapshot: 32/64 bit.

Possibly you have BLODA:

http://cygwin.com/acronyms#BLODA

cgf

--
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