This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libmudflap/23084] New: mudflap crash upon accept() with argement 2 and 3 as NULL


Mudflap crashes when it sees an accept in the form of:
accept(lsock, NULL, NULL)
and does not crash upon:
accept(lsock, &addr, &len);

The former case is - AFAIK - legal, quoting from the accept() manpage:
'When addr is NULL nothing is filled in.'

Attached is a minimal C program to reproduce this bug.

I tried this both on 4.0.0 and 4.0.1.

-- 
           Summary: mudflap crash upon accept() with argement 2 and 3 as
                    NULL
           Product: gcc
           Version: 4.0.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libmudflap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: syzop at vulnscan dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: gcc 4.0.1 20050720 (Red Hat 4.0.1-4)
GCC target triplet: Linux 2.6.11-1 -- Fedora Core 4 w/updates-testing


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23084


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]