public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: cppcheck 1.77 Segmentation fault (64-bit)
Date: Sat, 04 Feb 2017 00:08:00 -0000	[thread overview]
Message-ID: <ed80a1b5-754f-09f1-614d-b84aaf4ec18b@tiscali.co.uk> (raw)
In-Reply-To: <CAK-n8j4fu0QQ8-=1NYkGikWV5EMWBdkED7u9f50+w-tRLSabyw@mail.gmail.com>

On 29/01/17 21:04, Jim Reisert AD1C wrote:
> Best as I can tell, the seg fault is due to having installed the test
> version of gcc 6.0.  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.
>
> I invite you (Dave) to try the experiment yourself.  You would be wise
> to back up your Cygwin environment before doing this.

I've spent a little time looking into this. As per the stack track you 
supplied, cppcheck is falling over constructing a std::istringstream 
with a string passed in to initialise the stream. I'll need to debug 
this into the STL to work out exactly why the seg fault is occurring.

Note that there's more to this than simply constructing a 
std::istringstream - compiling the example given in [1] works fine, even 
if I use the same g++ switches used to build cppcheck. So there's 
something else going on...

Dave.

[1] 
http://www.cplusplus.com/reference/sstream/basic_istringstream/basic_istringstream/


--
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

  parent reply	other threads:[~2017-02-04  0:08 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
2017-01-29 22:55       ` David Stacey
2017-02-04  0:08     ` David Stacey [this message]
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=ed80a1b5-754f-09f1-614d-b84aaf4ec18b@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --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).