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:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=lOYpfiyZ6H5vMLYi BO6PvZB4MDVw2NDkn2x0XoV/UN/+4+PuO9xbJQrboghz/X/TfKfNAtLhO4TXxA/X zh7xYA6NoROE7+cGqPWyEE2fj9JY2J+e0B5O44SHTwsAeZp3LwBPAXe9ME9o1akO oRkolErpLoYy+Zv2YftLUBB2wd8= 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:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=osHDUA4CrNUuh8+mOmRcjg nyT3Y=; b=uKFm3Jo9PoZE5pyH08vK9KbV7Ng7y9BJxVhE1jReZ5A3+buOHbocUg Yz4vQ6iWcT7wYCloSJidrbhMXrSj1S/36tKqOtJitKjoR5HBBsgG8BT8DjdjRtf4 jq5GvWZdZCgsb7avxgutZST4oS6E0dg+m39+zfofyDEFrBcG0LKyg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=Geisert, geisert, H*u:6.1, H*UA:6.1 X-HELO: m0.truegem.net Subject: Re: Cygwin debugger crashes every time on following a unique_ptr To: cygwin AT cygwin DOT com References: <4ffe9ce5-8504-f009-2b19-098bdc9b1aef AT maxrnd DOT com> From: Mark Geisert Message-ID: <2400ad8a-beff-cc29-1e4d-464802fb3d7e@maxrnd.com> Date: Sun, 26 May 2019 00:51:53 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <4ffe9ce5-8504-f009-2b19-098bdc9b1aef@maxrnd.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. ..mark -- 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