public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: cppcheck 1.77 Segmentation fault (64-bit)
Date: Sun, 29 Jan 2017 22:13:00 -0000	[thread overview]
Message-ID: <e01c0360-3694-ac85-57f3-99b894c99095@t-online.de> (raw)
In-Reply-To: <CAK-n8j4fu0QQ8-=1NYkGikWV5EMWBdkED7u9f50+w-tRLSabyw@mail.gmail.com>

Jim Reisert AD1C wrote:
> Best as I can tell, the seg fault is due to having installed the test
> version of gcc 6.0.

I could reproduce the cppcheck segfault on 32-bit Cygin if 
libstd++6-6.3.0-1 is installed.

Possibly a variant of this problem:
https://cygwin.com/ml/cygwin/2017-01/msg00315.html

Downgrading /bin/cygstdc++-6.dll fixes the cppcheck crash.


>   Even uninstalling gcc 6.0 does not fix the
> problem.  I had to create an entirely new Cygwin-64 environment to get
> past the problem.

Did you possibly miss to downgrade libstdc++6 package ?
It is not visible if 'gcc' is entered in the Search field of setup.exe.

Christian


--
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:[~2017-01-29 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  2:57 Jim Reisert AD1C
2017-01-26 22:21 ` David Stacey
2017-01-29 21:04   ` Jim Reisert AD1C
2017-01-29 22:13     ` Christian Franke [this message]
2017-01-29 22:55       ` David Stacey
2017-02-04  0:08     ` David Stacey
2017-02-04 15:57       ` David Stacey
2017-02-08  6:20         ` Christian Franke

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=e01c0360-3694-ac85-57f3-99b894c99095@t-online.de \
    --to=christian.franke@t-online.de \
    --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).