A bug for Code::Blocks to work with CDB X64

User forums > Help

<< < (3/4) > >>

ollydbg:

--- Quote from: geoffzou on April 08, 2013, 04:05:24 am ---OK, I just can't give it a break. Considering I am new to the whole CB things, please give me more detailed advice on how to get it fixed. Where is the related source code located? How is it integrated with CB IDE. If I only want to look into the local piece of code, is it possible for me to rid compiling the whole code base from svn?

--- End quote ---
I'm not a CDB user, so I can't give much suggest, but at least some:
1, I think you need to lean how to build C::B, you can see a wiki page in Wiki
2, modify the debugger plugin source code, especially the files: cb_trunk\src\plugins\debuggergdb\cdb_driver.cpp
3, please note that all the debugger do is either parsing the messages from the CDB command line or send some command to CDB

Good luck!

geoffzou:

--- Quote from: ollydbg on April 08, 2013, 05:34:48 am ---
--- Quote from: geoffzou on April 08, 2013, 04:05:24 am ---OK, I just can't give it a break. Considering I am new to the whole CB things, please give me more detailed advice on how to get it fixed. Where is the related source code located? How is it integrated with CB IDE. If I only want to look into the local piece of code, is it possible for me to rid compiling the whole code base from svn?

--- End quote ---
I'm not a CDB user, so I can't give much suggest, but at least some:
1, I think you need to lean how to build C::B, you can see a wiki page in Wiki
2, modify the debugger plugin source code, especially the files: cb_trunk\src\plugins\debuggergdb\cdb_driver.cpp
3, please note that all the debugger do is either parsing the messages from the CDB command line or send some command to CDB

Good luck!

--- End quote ---

Are plugins of CB working with the IDE at the executable(process) level or source code level? I hope the debugger and the IDE interact as separate processes. If my hypothesis is valid, is there a sub-project for the CDB debugger integration that I can focus on?

oBFusCATed:

--- Quote from: geoffzou on April 08, 2013, 04:07:10 pm ---Are plugins of CB working with the IDE at the executable(process) level or source code level? I hope the debugger and the IDE interact as separate processes. If my hypothesis is valid, is there a sub-project for the CDB debugger integration that I can focus on?

--- End quote ---
The parser for the CDB's output is working in process and the code is in the debugger plugin (separate dll).

geoffzou:

--- Quote from: oBFusCATed on April 08, 2013, 04:39:12 pm ---
--- Quote from: geoffzou on April 08, 2013, 04:07:10 pm ---Are plugins of CB working with the IDE at the executable(process) level or source code level? I hope the debugger and the IDE interact as separate processes. If my hypothesis is valid, is there a sub-project for the CDB debugger integration that I can focus on?

--- End quote ---
The parser for the CDB's output is working in process and the code is in the debugger plugin (separate dll).

--- End quote ---

Here is my cbp file. This cbp compiles all the source code, but somehow, when I replace the original debugger.dll with my one, CB doesn't load it at all. Any magic here?

--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="Project_cb" />
<Option pch_mode="2" />
<Option compiler="gcc" />
<Build>
<Target title="default">
<Option output="debugger" prefix_auto="1" extension_auto="1" />
<Option type="3" />
<Option compiler="gcc" />
<Option host_application="$(#cb)/devel/codeblocks.exe" />
<Option run_host_application_in_terminal="0" />
<Compiler>
<Add option="-O2" />
<Add option="-pipe" />
<Add option="-mthreads" />
<Add option="-fmessage-length=0" />
<Add option="-fexceptions" />
<Add option="-Winvalid-pch" />
<Add option="-DBUILDING_PLUGIN" />
<Add option="-DHAVE_W32API_H" />
<Add option="-D__WXMSW__" />
<Add option="-DWXUSINGDLL" />
<Add option="-DcbDEBUG" />
<Add option="-DCB_PRECOMP" />
<Add option="-DWX_PRECOMP" />
<Add option="-DwxUSE_UNICODE" />
<Add directory="$(#cb)/include" />
<Add directory="$(#cb)/sdk/wxscintilla/include" />
<Add directory="$(#wx.include)" />
<Add directory="$(#wx.lib)/gcc_dll/mswu" />
<Add directory="$(#cb)/include/scripting/include" />
<Add directory="$(#cb)/include/scripting/sqplus" />
</Compiler>
<Linker>
<Add option="-mthreads" />
<Add library="codeblocks" />
<Add library="wxmsw28u" />
<Add directory="$(#cb)/devel" />
<Add directory="$(#wx.lib)/gcc_dll" />
</Linker>
<ExtraCommands>
<Add after="zip -j9 debugger.zip manifest.xml" />
<Add after="zip -j9 debugger.cbplugin debugger.dll debugger.zip" />
</ExtraCommands>
</Target>
</Build>
<ResourceCompiler>
<Add directory="../resources/Project_cb/" />
</ResourceCompiler>
<Unit filename="../cdb_commands.h" />
<Unit filename="../cdb_driver.cpp" />
<Unit filename="../cdb_driver.h" />
<Unit filename="../databreakpointdlg.cpp" />
<Unit filename="../databreakpointdlg.h" />
<Unit filename="../debugger_defs.cpp" />
<Unit filename="../debugger_defs.h" />
<Unit filename="../debuggerdriver.cpp" />
<Unit filename="../debuggerdriver.h" />
<Unit filename="../debuggergdb.cpp" />
<Unit filename="../debuggergdb.h" />
<Unit filename="../debuggeroptionsdlg.cpp" />
<Unit filename="../debuggeroptionsdlg.h" />
<Unit filename="../debuggeroptionsprjdlg.cpp" />
<Unit filename="../debuggeroptionsprjdlg.h" />
<Unit filename="../debuggerstate.cpp" />
<Unit filename="../debuggerstate.h" />
<Unit filename="../editbreakpointdlg.cpp" />
<Unit filename="../editbreakpointdlg.h" />
<Unit filename="../editwatchdlg.cpp" />
<Unit filename="../editwatchdlg.h" />
<Unit filename="../gdb_commands.h" />
<Unit filename="../gdb_driver.cpp" />
<Unit filename="../gdb_driver.h" />
<Unit filename="../parsewatchvalue.cpp" />
<Unit filename="../parsewatchvalue.h" />
<Unit filename="../remotedebugging.h" />
<Extensions>
<code_completion />
<envvars />
<debugger />
<lib_finder disable_auto="1" />
</Extensions>
</Project>
</CodeBlocks_project_file>

--- End code ---

oBFusCATed:

--- Quote from: geoffzou on May 14, 2013, 04:23:18 am ---Any magic here?

--- End quote ---
You need to use the same compiler and libraries used to compile codeblocks.exe failing to do so might cause this error.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version