From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118904 invoked by alias); 4 Feb 2017 00:08:27 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 118832 invoked by uid 89); 4 Feb 2017 00:08:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_COUK,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=wise, Reisert, ad1c, AD1C X-HELO: smtp-out-3.tiscali.co.uk Received: from smtp-out-3.tiscali.co.uk (HELO smtp-out-3.tiscali.co.uk) (62.24.135.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 04 Feb 2017 00:08:16 +0000 Received: from [192.168.1.4] ([79.68.219.73]) by smtp.talktalk.net with SMTP id ZnthcRXBbvKu9ZntlcUTk3; Sat, 04 Feb 2017 00:08:13 +0000 Subject: Re: cppcheck 1.77 Segmentation fault (64-bit) To: cygwin@cygwin.com References: <1461736e-51a3-3bb3-cbaf-90b6d41548a1@tiscali.co.uk> From: David Stacey Message-ID: Date: Sat, 04 Feb 2017 00:08:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfL0QNj8YpCRcUndFHJjoznu1Qhudj7S2aYI9lifwIqhQqulcrffrKHFAUCYhYGfj7SqQlYnXfw0CyhlbDPMFnoKzau/4lxlsUkZ9zXnqJADSgrq+LODS zCYKdFmhg8P6pqHsZP7VOLta5hD6kRUBWOuDpQwZIrKtsjljB03MuqM8 X-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00051.txt.bz2 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