From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>,
Raj Kumar <gaurav@iastate.edu>
Subject: Re: Cygwin debugger crashes every time on following a unique_ptr
Date: Sun, 26 May 2019 16:40:00 -0000 [thread overview]
Message-ID: <7a439630-5450-b41e-1f03-c93cfd356b67@dronecode.org.uk> (raw)
In-Reply-To: <4ffe9ce5-8504-f009-2b19-098bdc9b1aef@maxrnd.com>
On 25/05/2019 22:31, Mark Geisert wrote:
> Raj Kumar wrote:
> [...]
>> Adding a watch is equivalent to when in the gdb window I try and do
>> this: myCar.get()->currentPassengers. This crashes the GDB every time.
>> So the issue occurs when I try to follow the object pointed to by a
>> unique_ptr and try to get its attributes/variables.
>
> 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.
When debugging gdb with itself here, you'll need to use 'set
cygwin-exceptions on' to allow it to stop on exceptions inside the
cygwin DLL.
See https://cygwin.com/faq.html#faq.programming.debugging-cygwin
(This would be a lot more usable if gdb ignored exceptions inside the
specific functions where it makes sense to do that (e.g.
verifyable_object_isvalid, etc.), rather than anywhere in the cygwin
DLL, if someone wants to fix that...)
> To reproduce with OP's supplied source files in an otherwise clean
> directory:
> g++ -g -o raj *.cpp
> gdb raj
> [...]
> (gdb) b main
> (gdb) run
> (gdb) n
> (gdb) n
>
> At this point you'll be on line 14. Issue the OP's triggering command:
> (gdb) p myCar.get()->currentPassengers
> Segmentation fault (core dumped)
Thanks for the reproduction instructions.
This seems to be the issue discussed in [1], fixed by [2].
This fix is contained in the 8.2.1-1 Cygwin test release of gdb.
[1] https://sourceware.org/ml/gdb-patches/2018-06/msg00584.html
[2]
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=de52b9607d2623f18b7a7dbee3e1123d8d63f5da
--
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
prev parent reply other threads:[~2019-05-26 16:40 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
2019-05-26 16:40 ` Jon Turney [this message]
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=7a439630-5450-b41e-1f03-c93cfd356b67@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=gaurav@iastate.edu \
/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).