This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
Re: compiler replacement
by diotalevi (Canon) on Oct 12, 2002 at 19:32 UTC

    I'd like to hear about how /xff/ indicates buffer overflow code. Or do you mean to detect source code that intends to exploit a bug in other unrelated software? This is... rather pointless and makes life harder since it /deletes/ the file in question. Beyond that point there's always #include statements to bring in other files and you have no way to detect that. If you meant to see if these strings are being given to the compiler then you'll need to run the actual compilation unit through this. So... either this code is misguided (and ineffective) or I've missed something fundamental to this script.

    __SIG__ printf "You are here %08x\n", unpack "L!", unpack "P4", pack "L!", B:: +svref_2object(sub{})->OUTSIDE
Re: compiler replacement
by zentara (Cardinal) on Oct 13, 2002 at 13:55 UTC
    If you are looking for a true sourcefile scanner, try this:
    flawfinder