This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libmudflap/26446] Running large program compiled with mudflap aborts even before reaching main()
- From: "walter dot zimmer at dlr dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Feb 2006 17:43:10 -0000
- Subject: [Bug libmudflap/26446] Running large program compiled with mudflap aborts even before reaching main()
- References: <bug-26446-12167@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from walter dot zimmer at dlr dot de 2006-02-23 17:43 -------
(In reply to comment #1)
> Mudflap needs memory to set up runtime data structures, so you simply need more
> (virtual) memory.
Ok, I understand. Thanks!
> cat /proc/meminfo
MemTotal: 4038480 kB
[...]
SwapTotal: 8385912 kB
Seems like adding even more memory is no simple task :)
A quick calculation on the other hand rises the question, if this much memory
shouldn't be enough. It's about 3000 times the memory of the application (4mb).
Are there any tricks how to get mudflap to use less memory? Variables don't
work, as it exits before evaluating them, so it would have to be a compile time
option.
Sadly, this is already a reduced version of our binary, so we can't get this
smaller, so I guess we have to do without mudflap's services.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26446