DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B8898383541D
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 <ariel.burbaickij@gmail.com>,
        The Cygwin Mailing List <cygwin@cygwin.com>
References: <CANeJNHq8XMMpHb1UenhAb_wmNdJ3K-qwdz91iqCMjQFig3dkig@mail.gmail.com>
From: Jon Turney <jon.turney@dronecode.org.uk>
In-Reply-To: <CANeJNHq8XMMpHb1UenhAb_wmNdJ3K-qwdz91iqCMjQFig3dkig@mail.gmail.com>
Precedence: list
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

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 ?

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