https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82614
--- Comment #7 from Marco Castelluccio <mcastelluccio at mozilla dot com> --- (In reply to Martin Liška from comment #6) > (In reply to Marco Castelluccio from comment #5) > > (In reply to Martin Liška from comment #4) > > > (In reply to Marco Castelluccio from comment #3) > > > > > Thanks for the report Marco. Looks it comes from Firefox, am I right? > > > > > > > > Yes, that's correct. Actually, from a build of the JS shell. > > > > > > > > > Which version of GCC have you been using? > > > > > > > > The build was done with "gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 > > > > 20160609". > > > > > > > > We were also able to reproduce the crash with a gcda generated normally, > > > > without __gcov_dump. > > > > > > I see, not the GCC 5.x is not longer supported. Anyway, please paste > > > backtrace from gcov when the segfaults happens. > > > > I'm having a hard time installing debugging symbols here, I might have to > > build GCC from scratch. > > If you already have a debug build of GCC 6 lurking around, you could try if > > you could reproduce the crash yourself. > > Yes, but am I right that the gcda and gcno files attached are created with > GCC 5.4? > I can't reproduce the segfault on my machine. Please paste command line > invocation. Yes, they were created with GCC 5.4. Here's a crash report when I try to parse them with gcov-7: https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1725255, perhaps you can get the stacktrace from there. I will report back after we finish testing with GCC 6/7.
