public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/50393] New: free() invalid pointer in mio_expr
@ 2011-09-14  8:40 zeccav at gmail dot com
  2011-09-14  9:46 ` [Bug fortran/50393] " mikael at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: zeccav at gmail dot com @ 2011-09-14  8:40 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50393

             Bug #: 50393
           Summary: free() invalid pointer in mio_expr
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zeccav@gmail.com


Created attachment 25269
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25269
just compile it with MALLOC_CHECK_=1

free() invalid pointer in mio_expr


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/50393] free() invalid pointer in mio_expr
  2011-09-14  8:40 [Bug fortran/50393] New: free() invalid pointer in mio_expr zeccav at gmail dot com
@ 2011-09-14  9:46 ` mikael at gcc dot gnu.org
  2011-09-14 10:43 ` burnus at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: mikael at gcc dot gnu.org @ 2011-09-14  9:46 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50393

Mikael Morin <mikael at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikael at gcc dot gnu.org

--- Comment #1 from Mikael Morin <mikael at gcc dot gnu.org> 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?


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/50393] free() invalid pointer in mio_expr
  2011-09-14  8:40 [Bug fortran/50393] New: free() invalid pointer in mio_expr zeccav at gmail dot com
  2011-09-14  9:46 ` [Bug fortran/50393] " mikael at gcc dot gnu.org
@ 2011-09-14 10:43 ` burnus at gcc dot gnu.org
  2011-09-14 20:14 ` zeccav at gmail dot com
  2011-09-14 20:28 ` kargl at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: burnus at gcc dot gnu.org @ 2011-09-14 10:43 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50393

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/50393] free() invalid pointer in mio_expr
  2011-09-14  8:40 [Bug fortran/50393] New: free() invalid pointer in mio_expr zeccav at gmail dot com
  2011-09-14  9:46 ` [Bug fortran/50393] " mikael at gcc dot gnu.org
  2011-09-14 10:43 ` burnus at gcc dot gnu.org
@ 2011-09-14 20:14 ` zeccav at gmail dot com
  2011-09-14 20:28 ` kargl at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: zeccav at gmail dot com @ 2011-09-14 20:14 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50393

--- Comment #3 from Vittorio Zecca <zeccav at gmail dot com> 2011-09-14 20:03:44 UTC ---
It seems to work now, no free() error messages. Maybe you can close the issue.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/50393] free() invalid pointer in mio_expr
  2011-09-14  8:40 [Bug fortran/50393] New: free() invalid pointer in mio_expr zeccav at gmail dot com
                   ` (2 preceding siblings ...)
  2011-09-14 20:14 ` zeccav at gmail dot com
@ 2011-09-14 20:28 ` kargl at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: kargl at gcc dot gnu.org @ 2011-09-14 20:28 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50393

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |kargl at gcc dot gnu.org
         Resolution|                            |WORKSFORME

--- Comment #4 from kargl at gcc dot gnu.org 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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-09-14 20:16 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-14  8:40 [Bug fortran/50393] New: free() invalid pointer in mio_expr zeccav at gmail dot com
2011-09-14  9:46 ` [Bug fortran/50393] " mikael at gcc dot gnu.org
2011-09-14 10:43 ` burnus at gcc dot gnu.org
2011-09-14 20:14 ` zeccav at gmail dot com
2011-09-14 20:28 ` kargl at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).