I know I've heard about some semi-automated tools to help migrate C/C++ to JAVA or CLR .NET code in the past.
I've also heard of tools to help instrument code and replace dangerous code like strcpy, printf, malloc, free, et. al. with more secure / instrumented types of calls without breaking the original code's function.
I never paid too much attention, though now I'm thinking of a few pet projects that this could be desirable for.
What are the better free tools or methodologies to go from C/C++ to C# or JAVA or other managed type code environments?
What are the better free tools to help clean up unreliable / unsafe usages of things like malloc/free, printf, strcpy, et. al. with versions that are more safe against buffer overruns?
What tools might help semi-automatically reform makefiles or autoconfs or whatever to help the code compile with better / more modern compiler options, linker options, etc.
Things like stack smashing guards at compile time, better error detection, address space randomization, position independent code, no text relocations, whatever the "best practice" options are for a given platform that doesn't too hideously break most old code?
It seems that there are lots of codes out there that are just about on the verge of being non-functional / non-sensible with the newer stricter compilers, with the evolution of 32 bit -> 64 bit systems, with the advent of multi-core systems, with the advent of buffer overflow problems, et. al.
I'm thinking that a lot of the 'value' in many of the old programs isn't so much in what they're written in but in what useful jobs they perform regardless of their language or library use. So the main thing that can be done to continue to benefit from them is to clean them up, improve their portability to modern platforms / ABIs / compilers / OSs, and help their security / reliability / maintainability.
There have to be some decent tools to assist this semi-automaticallt but I haven't seen too much that seems very comprehensive, i.e. a malloc replacement here, a safe strings library there, some instrumentation or autoconf fixes there...
I've also heard of tools to help instrument code and replace dangerous code like strcpy, printf, malloc, free, et. al. with more secure / instrumented types of calls without breaking the original code's function.
I never paid too much attention, though now I'm thinking of a few pet projects that this could be desirable for.
What are the better free tools or methodologies to go from C/C++ to C# or JAVA or other managed type code environments?
What are the better free tools to help clean up unreliable / unsafe usages of things like malloc/free, printf, strcpy, et. al. with versions that are more safe against buffer overruns?
What tools might help semi-automatically reform makefiles or autoconfs or whatever to help the code compile with better / more modern compiler options, linker options, etc.
Things like stack smashing guards at compile time, better error detection, address space randomization, position independent code, no text relocations, whatever the "best practice" options are for a given platform that doesn't too hideously break most old code?
It seems that there are lots of codes out there that are just about on the verge of being non-functional / non-sensible with the newer stricter compilers, with the evolution of 32 bit -> 64 bit systems, with the advent of multi-core systems, with the advent of buffer overflow problems, et. al.
I'm thinking that a lot of the 'value' in many of the old programs isn't so much in what they're written in but in what useful jobs they perform regardless of their language or library use. So the main thing that can be done to continue to benefit from them is to clean them up, improve their portability to modern platforms / ABIs / compilers / OSs, and help their security / reliability / maintainability.
There have to be some decent tools to assist this semi-automaticallt but I haven't seen too much that seems very comprehensive, i.e. a malloc replacement here, a safe strings library there, some instrumentation or autoconf fixes there...