# How would you recommend I fuzz Autoware?

I have been trying to fuzz Autoware for quite sometime right now and one of the developers pointed out that I would need to generate a lot of the files at compile time. I am using Lifuzzer and I need to know how I am suppose to compile the codebase without actually running the software ( I do not have CUDA installed onto the server which I have installed the Autoware docker so I get error messages when trying out the demos) and how I would be able to modify the Makefile and which Makefile do I modify so that I can fuzz part of the code. Currently I am trying to fuzz the code in detection (ros/src/computing/perception).

edit retag close merge delete

Your question is unfortunately not easy to understand. What do you mean by "compile the codebase without actually running the software"? The compile and execute steps are completely separate for a compiled language like C++, which is what most of Autoware is implemented in. Autoware uses CMake to manage compilation, which is in turn used via the colcon tool. If you try to edit the Makefiles generated by CMake, they will just be overwritten the next time you run CMake or colcon. Additionally, which CMakeLists.txt files you need to modify depends on which part of the code you want to fuzz, and just saying "perception" does not narrow it down much because perception is something like 80% of the work in autonomous driving. You need to start by identifying a specific library or node you want to fuzz. You do not need CUDA if you use a recent version ...(more)