------- Comment #4 from fche at redhat dot com 2006-04-22 15:37 -------
(In reply to comment #3)
>
> I investigated further and found that it is not the size of the memory that
> matters. The problem seems to be that we also use fortran code, which is not
> mudflapped, but needs the gfortran library. The mudflapped C code uses
> malloc(), which gets wrapped into calls to __mfwrap_malloc(). Unfortunately,
> libgfortran also uses malloc(), which is instrumented by libmudflap but
> shouldn't, as this exactly is causing the error.
The link-time wrapping of malloc is designed precisely so that other
uninstrumented libraries that call malloc by name still get registered in the
libmudflap runtime. That way, pointers from these libraries may make their way
to an instrumented routine, and be used without error. Does
MUDFLAP_OPTIONS=-trace-calls produce anything?
--
fche at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26446
