Support

Troubleshooting

Instrumented code fails to compile

This may indeed happen, for example, if the instrumentation introduces a logging statement before super() in Java (which has to be the first statement in the constructor). You may have to make minor changes to the instrumented code to make it compile. Alternatively, you may revert to the source code for that specific file.

Runtime error from LLM API calls

First, ensure that the API key is set correctly (see the Model section). If the error persists, you may check the error message from the LLM. If you have triggered a rate limit, you may retry with a lower --parallel_num. If you have exceeded the context window, you may use a lower --chunk_size for instrumentation. For concolic testing, you may drop instrumentation for non-critical files, or switch to a different model (e.g. Claude-4.0 with 1M tokens).

FAQ

Which platforms and languages are supported?

ConcoLLMic has been primarily tested on Linux (or WSL) and macOS. In theory, any language and their combinations should be supported. In practice, we have tested ConcoLLMic on C, C++, Python, Java, and Go.

Bug Report

Still need help with ConcoLLMic? You are welcome to raise an issue on GitHub with a detailed bug report.

License

The source code of ConcoLLMic is dual licensed. It admits free use under the GPLv3 license for non-commercial use (which include academic and educational purposes). For commercial use, please contact us for a commercial license. For more details, please see the LICENSE file.