[bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-05-27 Thread Paul D. Smith
Update of bug #50790 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #3: This is a duplicate

[bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-05-01 Thread enrique olaizola
Follow-up Comment #2, bug #50790 (project make): If the issue is the garbled error message in the output then I think I found a solution for that. See bug 50909: https://savannah.gnu.org/bugs/?50909 ___ Reply to this item at:

RE: [bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-04-18 Thread Martin Dorey
==22022== Address 0x4caf710 is 0 bytes inside a block of size 200 free'd ==22022==at 0x4A0804B: free (vg_replace_malloc.c:534) ==22022==by 0x41EC52: read_all_makefiles (read.c:210) That was helpful, thanks. Reproduced with: martind@swiftboat:~/tmp/make-50790$ cat first.make default:;

Re: [bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-04-18 Thread Jan Ziak
On Tue, Apr 18, 2017 at 9:53 AM, Edward Welbourne wrote: > Jan Ziak (12 April 2017 20:07) >> Is this a make-4.2.1 bug, or a gcc-6.3.0 bug? The line numbers in the garbled >> error messages, in this case 79 and 84, are correct. > > Given its sensitivity to the specific

Re: [bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-04-18 Thread Edward Welbourne
Jan Ziak (12 April 2017 20:07) > Is this a make-4.2.1 bug, or a gcc-6.3.0 bug? The line numbers in the garbled > error messages, in this case 79 and 84, are correct. Given its sensitivity to the specific flags passed to gcc, it's natural to suppose it's a gcc bug. You can test by running gcc

[bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-04-18 Thread Jan Ziak
Follow-up Comment #1, bug #50790 (project make): It isn't a gcc bug. Please fix it in make-4.2.1+ source code: ==22022== Memcheck, a memory error detector ==22022== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==22022== Using Valgrind-3.12.0 and LibVEX; rerun with -h for

[bug #50790] Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4

2017-04-12 Thread Jan Ziak
URL: Summary: Some kind of memory corruption in error messages with gcc-6.3.0 -flto=4 Project: make Submitted by: atomsymbol Submitted on: Wed 12 Apr 2017 06:07:20 PM UTC Severity: 3