From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24810 invoked by alias); 13 Feb 2014 09:19:04 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 24491 invoked by uid 48); 13 Feb 2014 09:18:59 -0000 From: "lomato at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/60171] New: SEGFAULT when compiling with --coverage on travis-ci Date: Thu, 13 Feb 2014 09:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: gcov-profile X-Bugzilla-Version: 4.6.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lomato at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg01198.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60171 Bug ID: 60171 Summary: SEGFAULT when compiling with --coverage on travis-ci Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: lomato at gmail dot com I'm experiencing a bug when compiling and running a code on travis-ci. In 2 different projects, when added --coverage, they both crash. Travis-ci is an automated platform that doesn't allow me to have an interactive shell, but I can run gdb scripts on it. I've filed a bug on their github account, and they suggested me to open one here, to have help/suggestions from you too. Here you can find the bug opened on travis https://github.com/travis-ci/travis-ci/issues/1966 where you can watch the runs with the segfaults and the gdb runs. The strangest thing is that when backtracing on gdb, it returns me a meaningless line (the last one of the source file, a line with "}" ).