User forums > Using Code::Blocks
Features in Windows Debugger CDB running VS2010 compiler
oBFusCATed:
Also there are no technical issues integrating this plugin in the main source, just lack of a maintainer.
tigerbeard:
--- Quote from: oBFusCATed on March 08, 2016, 09:10:36 pm ---Probably this link http://wiki.codeblocks.org/index.php/Linking_the_plugin_to_a_Nightly_Build might help.
--- End quote ---
Ok, thanks. I stumbled across that description before, but had nothing to relate to. Now that a good reason to check that out.
I would have posted my log already, but currently go a very weird case that it would not compile. The problem does not seem to be the plugin, but the PDB file thats gernerated which is not recoginised by CDB. Even native WinDBG would not do it. The plugin returns right after the g command with status 0.
The weird thing is that cbd/Wincdb is for that test.exe not looking for the Test.pdb which is there but rather for an image001f0000.pdf or image001f0000.dbg. Internet does not seem to be full of people with that problem...
tigerbeard:
--- Quote ---The problem does not seem to be the plugin, but the PDB file thats gernerated which is not recoginised by CDB. Even native WinDBG would not do it. The plugin returns right after the g command with status 0.
--- End quote ---
Found that. Weird indeed.
The source was a blockade in the Build Option dialog; the LinkerSettings/Policy was empty. That caused the libs and linker options to be ignored. Thus the linker did not include the \Debug flag and the correct libs. Strangely it did not produce any.
The output PDB of course was not matching the exe any more, so CDB would not accept to load it. That caused to debug run to quit instantly. Why WinDbg did not complain about a pdb file mismatch remains a bit mysterious. I did not find a single mention in the web that CDB tries to load a pdb for an image instead of the module itself. Would be happy to understand that a bit better, but of course thats off topic to the C:B forum.
So I got the source but not the cause. Unfortunately I could not reproduce the effect to get that combobox to display nothing. Seem that it should get to its default value "Append target options to project options" in case anything is weird.
At least learned a lot about CBD in a short time 8)
Navigation
[0] Message Index
[*] Previous page
Go to full version