--- Comment #1 from vesselinpeev at hotmail dot com 2006-08-08 13:51
---
If both -fmudflap and -fmudflapth is specified, there is no problem. I read
about it at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26864
It says that a patch has been committed to mainline, i.e. what would be
by the
multithreaded mudflap
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libmudflap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: vesselinpeev at
--- Comment #1 from vesselinpeev at hotmail dot com 2006-08-02 20:27
---
I have tested on more gcc / glibc combinations. The mudflap violation occurs
with glibc 2.4 (the latest glibc version currently), whereas with versions
2.3.5 and 2.3.6, the following printed and occurs instead
dflap violation
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libmudflap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: vesselinpeev at hotmail dot com
GCC host
gcc dot gnu dot org
ReportedBy: vesselinpeev at hotmail dot com
GCC host triplet: UNCO Running large program compiled with
mudflap abort
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28536
