We're currently trying to get our binary mudflapped with gcc 4.1-20060217.
Compiling with -fmudflap works (for the C code; FFLAGS omits -fmudflap),
linking with -lmudflap is also no problem.
When calling the binary, we get:
bash> ./testbin
Operating system error: Success
Memory allocation failed
Gdb tells me that it doesn't even reach main(), and the mudflap environment
variables have no effect. I guess mudflap just gives up when beeing used on
such a large binary, but I don't find anything on this error messages on google
and I wonder if it's documented somewhere.
In any case, if the cause is a memory allocation problem of mudflap, perhaps
the error message should be more specific about what one can do or it should be
documented somewhere, so perhaps this is only a documentation enhancement
request.
If on the other hand debugging of a 4 mb executable should be supported, I
wonder what I can do to trace this error down.
--
Summary: Running large program compiled with mudflap aborts even
before reaching main()
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: libmudflap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: walter dot zimmer at dlr dot de
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26446
