public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin debugger crashes every time on following a unique_ptr
Date: Sun, 26 May 2019 16:05:00 -0000	[thread overview]
Message-ID: <50f5f3d4-40f1-77cd-be95-4572758bab90@SystematicSw.ab.ca> (raw)
In-Reply-To: <2400ad8a-beff-cc29-1e4d-464802fb3d7e@maxrnd.com>

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

  reply	other threads:[~2019-05-26 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-25 16:04 Raj Kumar
2019-05-25 21:31 ` Mark Geisert
2019-05-26  7:52   ` Mark Geisert
2019-05-26 16:05     ` Brian Inglis [this message]
2019-05-26 16:40   ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50f5f3d4-40f1-77cd-be95-4572758bab90@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).