Bug 50393 - free() invalid pointer in mio_expr
Summary: free() invalid pointer in mio_expr
Status: RESOLVED WORKSFORME
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.7.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-14 08:33 UTC by Vittorio Zecca
Modified: 2011-09-14 20:16 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments
just compile it with MALLOC_CHECK_=1 (206 bytes, text/x-fortran)
2011-09-14 08:33 UTC, Vittorio Zecca
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vittorio Zecca 2011-09-14 08:33:21 UTC
Created attachment 25269 [details]
just compile it with MALLOC_CHECK_=1

free() invalid pointer in mio_expr
Comment 1 Mikael Morin 2011-09-14 09:11:27 UTC
(In reply to comment #0)
> Created attachment 25269 [details]
> just compile it with MALLOC_CHECK_=1
> 
> free() invalid pointer in mio_expr

Valgrind doesn't complain on FreeBSD.
Did you manage to fix your mpfr issue?
Comment 2 Tobias Burnus 2011-09-14 10:33:35 UTC
(In reply to comment #1)
> > just compile it with MALLOC_CHECK_=1
> > free() invalid pointer in mio_expr
> Valgrind doesn't complain on FreeBSD.

No problems either on x86-64-linux (w/ MALLOC_CHECK_, MALLOC_PERTURB_ but also with valgrind).

Given that the code is rather standard, it must be either a local problem or one of the nasty race-condition bugs, which only trigger very rarely.
Comment 3 Vittorio Zecca 2011-09-14 20:03:44 UTC
It seems to work now, no free() error messages. Maybe you can close the issue.
Comment 4 kargl 2011-09-14 20:16:06 UTC
(In reply to comment #3)
> It seems to work now, no free() error messages. Maybe you can close the issue.

Again, thanks for the bug report.  This may also have been 
fixed by Mikael patch.  I'm closing this with a WORKSFORME
tag. FIXED might also apply.