From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-041.btinternet.com (mailomta31-re.btinternet.com [213.120.69.124]) by sourceware.org (Postfix) with ESMTPS id B8898383541D for ; Wed, 22 Jun 2022 08:38:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B8898383541D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-004.btmx-prd.synchronoss.net ([10.2.54.7]) by re-prd-fep-041.btinternet.com with ESMTP id <20220622083825.EXOV3283.re-prd-fep-041.btinternet.com@re-prd-rgout-004.btmx-prd.synchronoss.net>; Wed, 22 Jun 2022 09:38:25 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A901C2A814091 X-Originating-IP: [86.139.167.41] X-OWM-Source-IP: 86.139.167.41 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvfedrudefhedgtdegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeffkeeigfdujeehteduiefgjeeltdelgeelteekudetfedtffefhfeufefgueettdenucfkphepkeeirddufeelrdduieejrdegudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddthegnpdhinhgvthepkeeirddufeelrdduieejrdeguddpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedvpdhrtghpthhtoheprghrihgvlhdrsghurhgsrghitghkihhjsehgmhgrihhlrdgtohhmpdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomh X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.105] (86.139.167.41) by re-prd-rgout-004.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A901C2A814091; Wed, 22 Jun 2022 09:38:25 +0100 Message-ID: <703a2749-e144-8264-4001-4bdc9056445c@dronecode.org.uk> Date: Wed, 22 Jun 2022 09:38:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: dumper does not dump Content-Language: en-GB To: Ariel Burbaickij , The Cygwin Mailing List References: From: Jon Turney In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3570.6 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2022 08:38:29 -0000 On 22/06/2022 08:19, Ariel Burbaickij wrote: > Hello cygwin group, > I am facing the following issue: > there is GTK application reproducibly "core dumping" (in quotation marks > because so far there is no comfortable core file that we know and learnt to > love from native *NIX, of course) upon me selecting a certain menu entry. > Now, I went and enabled dumper (version 3.3.5) by means of setting CYGWIN > environment variable to > > error_start=c:\cygwin64\bin\dump.cmd > > with backslashes properly escaped and dump.cmd set to: > c:\cygwin64\bin\dumper.exe -d -c %1 %2 '-c' is not a valid option for dumper. Can you point out what documentation mentions that so we can fix it! It's awkward because a new terminal is started for dumper, which disappears almost immediately, but if you add 'pause' at the end of your .cmd file, you should see it. But I think you are overcomplicating things here: 'export CYGWIN=error_start=dumper' should work (or even 'error_start=gdb' if you're just going to load the core dump into gdb afterwards...) > I am on Windows 10 here. > > Now, all I get for it is following: > > *** starting debugger for pid 2876, tid 16112 > > after which it hangs indefinitely and nothing more happens. Cygwin is waiting for the debugger to attach, indefinitely since it never happens here. > Any ideas, suggestions how to move on here ?