<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="main" />
<Option pch_mode="2" />
<Option compiler="gcc" />
<Build>
<Target title="Release">
<Option output="main" prefix_auto="1" extension_auto="1" />
<Option object_output="." />
<Option type="1" />
<Option compiler="gcc" />
<Compiler>
<Add option="-O2" />
<Add directory="/usr/include" />
</Compiler>
<Linker>
<Add option="-s" />
</Linker>
</Target>
</Build>
<Compiler>
<Add option="-Wall" />
<Add directory="/usr/include" />
</Compiler>
<Unit filename="main.cpp" />
<Extensions>
<code_completion>
<search_path add="/usr/include" />
</code_completion>
<envvars />
<debugger />
</Extensions>
</Project>
</CodeBlocks_project_file>
#include <unistd.h>
#include <fcntl.h>
int main(int argc, char *argv[])
{
int fdFile = open("/dev/urandom", O_RDONLY);
close(fdFile);
return 0;
}
Anyhow, why do you think your problem is related to C:B?I'm gonna try to stay serious and ask, what else you think C::B parser problems could be related to.
Still not minimal.It's as minimal as I could get without taking a dive into the CodeBlocks source codes. I was unable to make the bug manifest in an artificial environment, so I decided to just cut it off the natural and hope it will behave deterministically.
Still not minimal.A little late response, sorry.
I can reproduce the problem.
ollydbg: Can you look at it?
ollydbgDebugging is not that hard, mainly, when you see a "#include xxxx" statement, you just call the "HandleInclude()" function inside the parser, and it should locate the "xxxx" file, and parse that included file.
It works for me in Windows either. I even mentioned that I had not been able to make the bug manifest in Ubuntu, so I was glad oBFusCATed confirmed it was reproducible. I think the only way to fix this is to debug it myself.
But... is there any reason to continue supporting the plugin anyway, considering there is a more stable, more functional and much easier to maintain alternative?If you looked a similar IDE(codelite), you will see it have two alternative cc engine, one is its native cc, and the other is the clang.
Debugging is not that hardRight. What's hard is to setup the environment with all those dependencies that need to be additionally compiled and installed. Btw. I've just overwrote my previous compilation just because I forgot to change the prefix, and spent some half an hour restoring it. Anyway, I can't reproduce the bug anymore. No idea, what made that happen. I did system update since then, installed many dependencies etc... could be anything.