This is the mail archive of the
mailing list for the Cygwin project.
Re: cppcheck 1.77 Segmentation fault (64-bit)
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Sat, 4 Feb 2017 00:08:09 +0000
- Subject: Re: cppcheck 1.77 Segmentation fault (64-bit)
- Authentication-results: sourceware.org; auth=none
- References: <CAK-n8j57fMX0fbwExi+4RmrKpX0W+0ujQaq=OWchwhTq2wBQxw@mail.gmail.com> <firstname.lastname@example.org> <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  works fine, even
if I use the same g++ switches used to build cppcheck. So there's
something else going on...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple