glibc??

In a program I am working on I get this message when it runs:

*** glibc detected *** ./a.out: free(): invalid next size (normal):
0x080e0f78 ***
======= Backtrace: =========
[...]

It does compile OK. This happens after some variables are deallocated
in a subroutine and before the next statement after the subroutine
call is executed.

What is a glibc, what class of problems does this message indicate?
--
Dieter Britz (britz<at>chem.au.dk)
.

Relevant Pages

  • Re: Compile Error
    ... I used the word subroutine because ... I can handle the compile part when it doesn't have a problem. ... On Error GoTo Err_btnDepartmentSeniority_Click ... Dim stDocName As String ...
    (microsoft.public.access.gettingstarted)
  • Re: Fortran module checking
    ... Or are there compile options that should be invoked to ensure that USE ... finding or understanding Fortran module variables. ... end subroutine assign_values ...
    (comp.lang.fortran)
  • Re: How can I secure this small code ?
    ... main program and a simple subroutine. ... END PROGRAM ess ... My problem is that if I increase the precision at compile time for the ...
    (comp.lang.fortran)
  • Re: Problem with log function - Intel fortran compiler under Linux
    ... reals, others double-precision reals. ... especially as the compile options influence the place ... Turn on array bounds checking ... the END statements need to be promoted to end subroutine or end ...
    (comp.lang.fortran)
  • Re: Bus error/ segmentation fault--help?
    ... When I compile with the intel fortran compiler, ... This subroutine integrates the function y3 up one step, ... implicit double precision ... block which is explicitly "explicit" but not recommended in practice. ...
    (comp.lang.fortran)