public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
Date: Wed, 27 Sep 2017 23:43:00 -0000	[thread overview]
Message-ID: <fbaad8f7-062d-75ae-ae68-22fa940108d8@gmail.com> (raw)
In-Reply-To: <59c94bf0.b5329d0a.b3138.234e@mx.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]

On 09/25/2017 06:33 PM, Steven Penny wrote:
> On Mon, 25 Sep 2017 14:17:28, JonY wrote:
>> You can actually use Cygwin gdb to debug and see what went wrong,
>> assuming the debug symbols are around.
>>
>> Sorry if I'm not much help, kind of busy these days.
> 
> New command:
> 
> x86_64-w64-mingw32-g++ -g -static -o z z.cpp
> 
> Output:
> 
> (gdb) run
> Starting program: /tmp/z [New Thread 5956.0xfe4]
> Program received signal SIGSEGV, Segmentation fault.
> std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream.tcc:51
> 51 /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream.tcc: No such file or directory.
> (gdb) backtrace
> #0  std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
>    at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>   
> mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>    ostream.tcc:51
> #1  0x000000000049ece9 in std::__ostream_insert<char,
> std::char_traits<char> >
>  (__out=...,  __s=__s@entry=0x4ab031 <std::piecewise_construct+1> "cout
> test\n", __n=10)
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream_insert.h:82
> #2  0x00000000004a3547 in std::operator<< <std::char_traits<char> > (
>  __out=..., __s=0x4ab031 <std::piecewise_construct+1> "cout test\n")
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/std/
>  ostream:561
> #3  0x00000000004015e0 in main () at z.cpp:3
> 

Looks like the ostream is not properly initialized, all the C++
constructors involved makes it even more messy to debug.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

  reply	other threads:[~2017-09-27 23:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20 16:19 JonY
2017-08-21  1:57 ` Steven Penny
2017-08-21  2:45   ` Steven Penny
2017-08-22  2:22     ` Steven Penny
2017-08-22 12:47       ` JonY
2017-09-19 23:14         ` Steven Penny
2017-09-21  0:10           ` Steven Penny
2017-09-24  0:49             ` JonY
2017-09-24  3:07               ` Steven Penny
2017-09-25  1:53               ` Steven Penny
2017-09-25 14:18                 ` JonY
2017-09-25 18:33                   ` Steven Penny
2017-09-27 23:43                     ` JonY [this message]
2017-09-28  4:13                       ` Steven Penny
2017-09-25 16:43                 ` Hans-Bernhard Bröker
2017-09-25 18:44                   ` Steven Penny
2017-09-25 20:04                     ` Hans-Bernhard Bröker
2017-09-27  4:35                       ` Andrey Repin
2017-10-17 11:47 ` Steven Penny
2017-10-18  7:30   ` JonY

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=fbaad8f7-062d-75ae-ae68-22fa940108d8@gmail.com \
    --to=10walls@gmail.com \
    --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).