DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fTHDtjx5OTpLsSrL
	MD06K0Z5b8VcN+dzOMjldvWVGSzYp5qQ4Lsg5ENOJKUWRb42GmKz6IKqKx5b2Kv0
	Wy0Or7cpEBdq94n/kmWcM+VyP4QzYhA9rgf0MuVLGD64Ce0SmAWfUdkHRz836WjV
	p4XTf/magEYAWRsHpsIT5IPxirg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: Cygwin debugger crashes every time on following a unique_ptr
To: cygwin@cygwin.com
References: <CAECqvgfWPBo0VmYk=EG14vQkK-L7f4zGZ==pv-jSMt31vhavZw@mail.gmail.com> <4ffe9ce5-8504-f009-2b19-098bdc9b1aef@maxrnd.com> <2400ad8a-beff-cc29-1e4d-464802fb3d7e@maxrnd.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Openpgp: preference=signencrypt
Message-ID: <50f5f3d4-40f1-77cd-be95-4572758bab90@SystematicSw.ab.ca>
Date: Sun, 26 May 2019 10:05:24 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <2400ad8a-beff-cc29-1e4d-464802fb3d7e@maxrnd.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 2019-05-26 01:51, Mark Geisert wrote:
> Mark Geisert wrote:
>> I can confirm this issue.  The fault is reported by Cygwin's memcpy().  I'm
>> having a heck of a time trying to get a gdb backtrace to show what in gdb itself
>> is likely calling memcpy() with a bad arg.
> This seems to be a regression in gdb 8.1.1.  If you downgrade to gdb 8.0.1 on
> Cygwin the fault does not occur.  Obviously just a workaround.
> I'm curious which version of gdb the OP was using within CLion.  In any case
> this issue should be pointed out upstream (to the gdb developers).  It doesn't
> seem to be a Cygwin issue after all.
You should follow JetBrains debugger problem reporting guidelines (as you should
Cygwin's) if that is relevant to your use:
	https://intellij-support.jetbrains.com/hc/en-us/articles/206560589-Debugger-doesn-t-stop-on-a-breakpoint-Debugger-shows-Command-timed-out-What-to-do-

You should push this back to JetBrains for proper reproduction and diagnosis (if
Cygwin volunteers can do it in hours, JetBrains should have some employees
capable to do so) and have them report it to their upstream, which may be
https://sourceware.org/gdb/ also hosted on SourceWare like Cygwin.

CLion 2019.1 may now support gdb 8.1:
	https://intellij-support.jetbrains.com/hc/en-us/articles/206556469-What-compiler-debugger-can-I-use-within-CLion-
and fixes are available in upgrades:
	https://sourceware.org/gdb/news/
but below reports CLion 2018.1.6 uses gdb 8.0.1 - you should not use newer gdb
capabilities than supported by the installed release:
	https://confluence.jetbrains.com/display/CLION/Third-Party+Software+Used+by+CLion
and that info should be available for each release and up to date for the
current release.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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