Author Topic: [OT] unofficial MinGW GDB gdb with python released  (Read 174552 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #150 on: October 09, 2013, 03:12:17 am »
Bump: a new release is here, it fix a bug in FYI: GDB has a big bug to support MinGW GCC (4.7.x and later), please see the first page [OT] unofficial MinGW GDB gdb with python released for more details. Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #151 on: January 14, 2014, 01:29:35 am »
Bump: a new release 2014-01-14 is here. Updated page [OT] unofficial MinGW GDB gdb with python released gives you more details. Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #152 on: May 23, 2014, 03:07:14 am »
Updated.
2014-05-23
gdb2014-05-23.zip with patches against GDB GIT HEAD released. The main change in my patches from 2014-01-14 is that is fix a Bug 15806 Some fields in async MI events get escaped twice.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9506
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #153 on: January 28, 2016, 08:50:49 pm »
...long time no update...

As the debugger in TDM 5.1.0 still crashes for wx projects in general and TDM does not seem to fix it shortly, I'd like to see an update of this one, if possible.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #154 on: January 29, 2016, 01:32:45 pm »
...long time no update...

As the debugger in TDM 5.1.0 still crashes for wx projects in general and TDM does not seem to fix it shortly, I'd like to see an update of this one, if possible.
I personally build GDB months ago(I have not uploaded yet), I will build and upload the GDB git head this weekend
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #155 on: January 30, 2016, 08:32:37 am »
FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9506
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #156 on: January 30, 2016, 10:37:10 am »
FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.
Great, thanks! I'll definitely give it a shot. (I have no other choice anyways... LOL.)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9506
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #157 on: January 31, 2016, 05:52:32 pm »
FYI: Hi all, I have release a new build, which is GDB 2016-01-30, see the updated first post  [OT] unofficial MinGW GDB gdb with python released for details.
Well too bad. Now this debugger also fails to debug wxWidgets applications on Windows. The error is:

Quote
[debug]Error while reading shared library symbols for D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll:
[debug]D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll: error reading symbols
[debug]C:/crossdev/src/gdb-7.9.1/gdb/buildsym.c:1023: internal-error: prepare_for_building: Assertion `current_subfile == NULL' failed.
[debug]A problem internal to GDB has been detected,
[debug]further debugging may prove unreliable.
[debug]This is a bug, please report it.  For instructions, see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]This application has requested the Runtime to terminate it in an unusual way.
[debug]Please contact the application's support team for more information.

Does it work for you?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9506
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #158 on: January 31, 2016, 06:13:09 pm »
Well too bad. Now this debugger also fails to debug wxWidgets applications on Windows. The error is:
Aaaarg! nevermind - I picked the wrong debugger.
@Teodor: Is it possible the clearly show the name of the debugger chosen before a debug session starts? This happens rather often to me... as I switch often...

However - I see another issue: "Import error: site" and that's it. :-/ Looks like the python stuff is broken for me...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12069
    • Travis build status
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #159 on: January 31, 2016, 06:25:05 pm »
You want to see the name of the selected debugger configuration, right?
I think we print the path to the debugger already.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9506
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #160 on: January 31, 2016, 07:39:37 pm »
I think we print the path to the debugger already.
Yes, we do. And on the very top the debugger configuration is shown as well. This can be well overseen. Any change to at least colour the debugger config in blue, bold or alike?

And no fun: This debugger CRASHES with wx, too. I thought it would not, but after adding Python (32 bit) DLL and PATH I see this crash:

[debug]Error while reading shared library symbols for D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll:
[debug]D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll: error reading symbols
[debug]../../binutils-gdb/gdb/buildsym.c:1036: internal-error: void prepare_for_building(const char*, CORE_ADDR): Assertion `current_subfile == NULL' failed.
[debug]A problem internal to GDB has been detected,
[debug]further debugging may prove unreliable.
[debug]This is a bug, please report it.  For instructions, see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]This application has requested the Runtime to terminate it in an unusual way.
[debug]Please contact the application's support team for more information.


Anybody that can confirm the issue? It also happens on the command line, btw. I am trying to debug the debug version of Code::Blocks as you see. standard "Hello World" works.


Edit: Its the same error as with TDM now, btw.. Not the very same, as the path differs. So its really the new ollydbg debugger. I need to switch back to the old one. :-(
« Last Edit: January 31, 2016, 07:42:46 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12069
    • Travis build status
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #161 on: January 31, 2016, 08:01:47 pm »
Any change to at least colour the debugger config in blue, bold or alike?
It should be possible. Probably it will be easiest to tweak it to the way you like it.:)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #162 on: February 01, 2016, 06:09:24 am »
I think we print the path to the debugger already.
Yes, we do. And on the very top the debugger configuration is shown as well. This can be well overseen. Any change to at least colour the debugger config in blue, bold or alike?

And no fun: This debugger CRASHES with wx, too. I thought it would not, but after adding Python (32 bit) DLL and PATH I see this crash:

[debug]Error while reading shared library symbols for D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll:
[debug]D:\Devel\CodeBlocks\src\devel\wxmsw28u_gcc_custom.dll: error reading symbols
[debug]../../binutils-gdb/gdb/buildsym.c:1036: internal-error: void prepare_for_building(const char*, CORE_ADDR): Assertion `current_subfile == NULL' failed.
[debug]A problem internal to GDB has been detected,
[debug]further debugging may prove unreliable.
[debug]This is a bug, please report it.  For instructions, see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]This application has requested the Runtime to terminate it in an unusual way.
[debug]Please contact the application's support team for more information.


Anybody that can confirm the issue? It also happens on the command line, btw. I am trying to debug the debug version of Code::Blocks as you see. standard "Hello World" works.


Edit: Its the same error as with TDM now, btw.. Not the very same, as the path differs. So its really the new ollydbg debugger. I need to switch back to the old one. :-(
I don't have this kind of issue in my system, as I'm using debug version of wx2.8 and debug version of wx 3.0.2 and git header. This is what I am going to do:
1, use some release version of wx 2.8
2, I will try to use GDB from TDM and see whether it has such error.

Will report back soon.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #163 on: February 01, 2016, 07:13:57 am »
Hi, Morten, I guess this is an GCC issue comes from TDM's GCC. I just have those test environment:
1, I have a wx 2.8 release which is built by "MinGW-Build 4.8.1 dw2" (Note MinGW-Build 4.8.1 comes from MinGW-W64 project)
2, I build C::B against this wx 2.8, but I build it with "MinGW-Build 4.9. dw2".
3, I can debug C::B under my build GDB(2016-01-30) without any issue.

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5230
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [OT] unofficial MinGW GDB gdb with python released
« Reply #164 on: February 01, 2016, 07:43:36 am »
Morten, I did another dummy test.

I just download the binary files from our 16.01 release, and unzip it.
I then create a very dummy project, and I set the output file to the codeblocks.exe and add all the necessary args like below:
Code: [Select]
--debug-log --no-dde --no-check-associations --multiple-instance --no-splash-screen --verbose -p debug
Then I can debug this dummy project.
Then I see I can correctly debug the codeblocks.exe(also no debug information inside the exe and dlls), and I see all dlls are loaded correctly, and no error reported. This means my GDB dose not report the error when loading the wx dll build from TDM gcc(I think our 16.01 release binary was build from TDM GCC, right?)

Here is the full log, you can have a look, I can pause the debugee, and print all the shared libraries:
Code: [Select]
[debug]Command-line: E:\code\gdb\mybuild\bin\gdb.exe -nx -fullname -quiet  -args E:/code/cb/16.01/codeblocks-16.01-nosetup/codeblocks.exe
[debug]Working dir : D:\temp\hihihi

Starting debugger: E:\code\gdb\mybuild\bin\gdb.exe -nx -fullname -quiet  -args E:/code/cb/16.01/codeblocks-16.01-nosetup/codeblocks.exe
done

[debug]> set prompt >>>>>>cb_gdb:
[debug]Skip initializing the scripting!

Setting breakpoints

[debug]Reading symbols from E:/code/cb/16.01/codeblocks-16.01-nosetup/codeblocks.exe...(no debugging symbols found)...done.
[debug](gdb) >>>>>>cb_gdb:
[debug]> show version

Reading symbols from E:/code/cb/16.01/codeblocks-16.01-nosetup/codeblocks.exe...(no debugging symbols found)...done.

[debug]GNU gdb (GDB) 7.10.50.20160130-git
[debug]Copyright (C) 2016 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "mingw32".
[debug]Type "show configuration" for configuration details.
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]Find the GDB manual and other documentation resources online at:
[debug]<http://www.gnu.org/software/gdb/documentation/>.
[debug]For help, type "help".
[debug]Type "apropos word" to search for commands related to "word".
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.10.50.20160130-git

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor intel
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source E:\code\gdb\mybuild\bin\my.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory D:/temp/hihihi/
[debug]Source directories searched: D:/temp/hihihi;$cdir;$cwd
[debug]>>>>>>cb_gdb:
[debug]> set args --debug-log --no-dde --no-check-associations --multiple-instance --no-splash-screen --verbose -p debug
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]Starting program: E:\code\cb\16.01\codeblocks-16.01-nosetup\codeblocks.exe --debug-log --no-dde --no-check-associations --multiple-instance --no-splash-screen --verbose -p debug

Child process PID: 2948

[debug][New Thread 2948.0xe64]
[debug][New Thread 2948.0xf4c]
[debug][New Thread 2948.0x4b4]
[debug][New Thread 2948.0xcf8]
[debug][New Thread 2948.0x9e8]
[debug][New Thread 2948.0x758]
[debug][New Thread 2948.0x2e4]
[debug][New Thread 2948.0x5d4]
[debug][New Thread 2948.0xb8c]
[debug][New Thread 2948.0xe74]

Trying to interrupt process with pid: 2948; child pid: 2948 gdb pid: 2524

[debug][Thread 2948.0xe74 exited with code 0]
[debug][New Thread 2948.0xea4]
[debug]Thread 11 received signal SIGTRAP, Trace/breakpoint trap.
[debug][Switching to Thread 2948.0xea4]
[debug]0x7c90120f in ntdll!DbgBreakPoint () from C:\WINDOWS\system32\ntdll.dll
[debug]>>>>>>cb_gdb:

In ntdll!DbgBreakPoint () (C:\WINDOWS\system32\ntdll.dll)

[debug]> bt 30
[debug]#0  0x7c90120f in ntdll!DbgBreakPoint () from C:\WINDOWS\system32\ntdll.dll
[debug]#1  0x7c952119 in ntdll!DbgUiRemoteBreakin () from C:\WINDOWS\system32\ntdll.dll
[debug]#2  0x00000005 in ?? ()
[debug]#3  0x00000004 in ?? ()
[debug]#4  0x00000001 in ?? ()
[debug]#5  0x06feffd0 in ?? ()
[debug]#6  0x00000000 in ?? ()
[debug]>>>>>>cb_gdb:

> info shared

[debug]> info shared
[debug]From        To          Syms Read   Shared Object Library
[debug]0x7c901000  0x7c9b1ee0  Yes (*)     C:\WINDOWS\system32\ntdll.dll
[debug]0x7c801000  0x7c8f5cd8  Yes (*)     C:\WINDOWS\system32\kernel32.dll
[debug]0x5d091000  0x5d12907c  Yes (*)     C:\WINDOWS\system32\comctl32.dll
[debug]0x77dd1000  0x77e6aaf8  Yes (*)     C:\WINDOWS\system32\advapi32.dll
[debug]0x77e71000  0x77f02554  Yes (*)     C:\WINDOWS\system32\rpcrt4.dll
[debug]0x77fe1000  0x77ff0888  Yes (*)     C:\WINDOWS\system32\secur32.dll
[debug]0x77f11000  0x77f58878  Yes (*)     C:\WINDOWS\system32\gdi32.dll
[debug]0x7e411000  0x7e4a0de4  Yes (*)     C:\WINDOWS\system32\user32.dll
[debug]0x77c11000  0x77c67d74  Yes (*)     C:\WINDOWS\system32\msvcrt.dll
[debug]0x7c9c1000  0x7d1d6510  Yes (*)     C:\WINDOWS\system32\shell32.dll
[debug]0x77f61000  0x77fd59d4  Yes (*)     C:\WINDOWS\system32\shlwapi.dll
[debug]0x76781000  0x767881cc  Yes (*)     C:\WINDOWS\system32\shfolder.dll
[debug]0x6cc41000  0x6d3dcdc8  Yes         E:\code\cb\16.01\codeblocks-16.01-nosetup\wxmsw28u_gcc_cb.dll
[debug]0x763b1000  0x763f84dc  Yes (*)     C:\WINDOWS\system32\comdlg32.dll
[debug]0x774e1000  0x7761d110  Yes (*)     C:\WINDOWS\system32\ole32.dll
[debug]0x77121000  0x771aa42c  Yes (*)     C:\WINDOWS\system32\oleaut32.dll
[debug]0x76b41000  0x76b6c8b4  Yes (*)     C:\WINDOWS\system32\winmm.dll
[debug]0x73001000  0x7302551c  Yes (*)     C:\WINDOWS\system32\winspool.drv
[debug]0x71ad1000  0x71ad804c  Yes (*)     C:\WINDOWS\system32\wsock32.dll
[debug]0x71ab1000  0x71ac6dc8  Yes (*)     C:\WINDOWS\system32\ws2_32.dll
[debug]0x71aa1000  0x71aa7320  Yes (*)     C:\WINDOWS\system32\ws2help.dll
[debug]0x617c1000  0x61dfe600  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\codeblocks.dll
[debug]0x6e441000  0x6e50a86c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxpropgrid.dll
[debug]0x66e41000  0x66e4c3d0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\exchndl.dll
[debug]0x61541000  0x6157b2fc  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\mgwhelp.dll
[debug]0x03001000  0x03148ce4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\dbghelp.dll
[debug]0x76bf1000  0x76bfa3c4  Yes (*)     C:\WINDOWS\system32\psapi.dll
[debug]0x77c01000  0x77c07300  Yes (*)     C:\WINDOWS\system32\version.dll
[debug]0x76391000  0x763acc6c  Yes (*)     C:\WINDOWS\system32\imm32.dll
[debug]0x629c1000  0x629c828e  Yes (*)     C:\WINDOWS\system32\lpk.dll
[debug]0x74d91000  0x74dfa696  Yes (*)     C:\WINDOWS\system32\usp10.dll
[debug]0x773d1000  0x774d2e2c  Yes (*)     C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll
[debug]0x74721000  0x7476bc4c  Yes (*)     C:\WINDOWS\system32\MSCTF.dll
[debug]0x755c1000  0x755edba0  Yes (*)     C:\WINDOWS\system32\MSCTFIME.IME
[debug]0x01511000  0x017d4448  Yes (*)     C:\WINDOWS\system32\xpsp2res.dll
[debug]0x4b401000  0x4b4853c2  Yes (*)     C:\WINDOWS\system32\msftedit.dll
[debug]0x6bd81000  0x6bdbd310  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\abbreviations.dll
[debug]0x712c1000  0x7139e8cc  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\astyle.dll
[debug]0x64381000  0x643b1c7c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\autosave.dll
[debug]0x6fc01000  0x6fcaf158  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\AutoVersioning.dll
[debug]0x6f741000  0x6f795d54  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\BrowseTracker.dll
[debug]0x6e141000  0x6e18c86c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\byogames.dll
[debug]0x6ca41000  0x6ca73f64  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\cb_koders.dll
[debug]0x64b81000  0x64bab628  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\Cccc.dll
[debug]0x6af01000  0x6af3c320  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\classwizard.dll
[debug]0x65e81000  0x65fef374  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\codecompletion.dll
[debug]0x67f01000  0x67fdc8ec  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\codesnippets.dll
[debug]0x69f01000  0x69f873c8  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\codestat.dll
[debug]0x03581000  0x036a802c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\compiler.dll
[debug]0x62841000  0x6286a56c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\copystrings.dll
[debug]0x6c081000  0x6c0b8380  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\CppCheck.dll
[debug]0x6f201000  0x6f2852a0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\Cscope.dll
[debug]0x6d881000  0x6d965e50  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\debugger.dll
[debug]0x649c1000  0x649f8640  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\defaultmimehandler.dll
[debug]0x6fac1000  0x6fb16be0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\devpakupdater.dll
[debug]0x6c541000  0x6c5c3d44  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\DoxyBlocks.dll
[debug]0x674c1000  0x674fd9b4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\DragScroll.dll
[debug]0x020b1000  0x020e502c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\EditorConfig.dll
[debug]0x67681000  0x676bf790  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\EditorTweaks.dll
[debug]0x6a701000  0x6a73d5c8  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\envvars.dll
[debug]0x657c1000  0x65a0b178  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\Exporter.dll
[debug]0x63081000  0x6316bc40  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\FileManager.dll
[debug]0x6b141000  0x6b2d4710  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\FortranProject.dll
[debug]0x036b1000  0x0375af4c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\headerfixup.dll
[debug]0x03761000  0x03861cd4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\help_plugin.dll
[debug]0x7e4b1000  0x7e538bee  Yes (*)     C:\WINDOWS\system32\hhctrl.ocx
[debug]0x62e01000  0x62ef0a24  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\HexEditor.dll
[debug]0x68d81000  0x68db8324  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\IncrementalSearch.dll
[debug]0x03871000  0x03918774  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\keybinder.dll
[debug]0x68001000  0x680ea334  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\lib_finder.dll
[debug]0x03921000  0x0399a990  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxflatnotebook.dll
[debug]0x70201000  0x7022b740  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\MouseSap.dll
[debug]0x64801000  0x648f5d1c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\NassiShneiderman.dll
[debug]0x039a1000  0x039d7120  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\OccurrencesHighlighting.dll
[debug]0x69041000  0x6906c75c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\openfileslist.dll
[debug]0x6edc1000  0x6ee4a6d4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\Profiler.dll
[debug]0x705c1000  0x70602be0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\ProjectOptionsManipulator.dll
[debug]0x70501000  0x70556274  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\projectsimporter.dll
[debug]0x69641000  0x69670ad0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\RegExTestbed.dll
[debug]0x039e1000  0x03a1515c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\ReopenEditor.dll
[debug]0x6a0c1000  0x6a0ea578  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\rndgen.dll
[debug]0x63c01000  0x63c70bd0  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\scriptedwizard.dll
[debug]0x6a981000  0x6a9ae9b4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentCpp.dll
[debug]0x64e41000  0x64e69560  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentFortran.dll
[debug]0x68d41000  0x68d6b6a8  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentHDL.dll
[debug]0x61501000  0x61529500  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentLua.dll
[debug]0x6ba41000  0x6ba6954c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentPascal.dll
[debug]0x68501000  0x68529508  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentPython.dll
[debug]0x03a21000  0x03a4a5dc  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SmartIndentXML.dll
[debug]0x03a51000  0x03b59894  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SpellChecker.dll
[debug]0x6e281000  0x6e2bc544  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\SymTab.dll
[debug]0x69d41000  0x69dac528  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\ThreadSearch.dll
[debug]0x638c1000  0x639003fc  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxcustombutton.dll
[debug]0x6bac1000  0x6bb58400  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\todo.dll
[debug]0x03b61000  0x03bbe074  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\ToolsPlus.dll
[debug]0x03bc1000  0x03be8478  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\wxsmith.dll
[debug]0x66f41000  0x672da5e4  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxsmithlib.dll
[debug]0x6ab41000  0x6abc1164  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\wxSmithAui.dll
[debug]0x04851000  0x049a7844  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\wxSmithContribItems.dll
[debug]0x6da81000  0x6dad6210  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxchartctrl.dll
[debug]0x66441000  0x66473c30  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wximagepanel.dll
[debug]0x6ed41000  0x6eda2c8c  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxkwic.dll
[debug]0x70c01000  0x70c5d0a8  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxled.dll
[debug]0x049b1000  0x04a5b094  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxmathplot.dll
[debug]0x6f3c1000  0x6f3fb210  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxspeedbutton.dll
[debug]0x04a61000  0x04ab70d8  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\wxtreelist.dll
[debug]0x62301000  0x6232b604  Yes (*)     E:\code\cb\16.01\codeblocks-16.01-nosetup\share\CodeBlocks\plugins\xpmanifest.dll
[debug]0x76381000  0x7638403c  Yes (*)     C:\WINDOWS\system32\msimg32.dll
[debug](*): Shared library is missing debugging information.
...

Oh, but I see:
Code: [Select]
0x6cc41000  0x6d3dcdc8  Yes         E:\code\cb\16.01\codeblocks-16.01-nosetup\wxmsw28u_gcc_cb.dll
There is no * mark, and we have "debug" information in the "wxmsw28u_gcc_cb.dll"? Did you locally strip this dll in your computer? This may destroy the dll if the "strip" command has some issue. (I remember the exchdl.dll has such issue, so we can't strip on it)
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.