User forums > General (but related to Code::Blocks)

[OT] unofficial MinGW GDB gdb with python released

<< < (19/35) > >>

ollydbg:
Finally, I have successfully build gdb.exe with expat-1.dll support. Here are the major steps, I hope it can help others to build gdb.exe himself.

You need MSYS and MinGW installed in your system.

First, you need to build expat library.
1, Download the expat source.
2, Suppose your expat2.0.1 source code was located in c:\expat2.0.1, and you would like the generated dll installed in c:\install_expat
In MSYS, under /c/expat2.0.1, entering these command:

--- Code: ---./configure -prefix=/c/install_expat --enable-shared
--- End code ---
3, make[press enter]
4, make install[press enter]
Then, you will have all the files in c:\install_expat. also, don't forget to run the strip command to strip the debug information. for example:
strip expat-1.dll will remove the strip information in this dll, and reduce the dll file size.

Second, build gdb
You need to copy all the files under c:\install_expat to c:\mingw, I suppose you have install MinGW in "c:\mingw", so, now, the compiler can find both the headers and libraries.

1, download the gdb source file, and unzip them, eg, they are extract to c:\gdb2010XXX
2, Create two empty folders, one is c:\obj_gdb, and the other is c:\install_gdb
3, in MSYS command, go to /c/obj_gdb
4, run these command:

--- Code: ---../gdb2010XXX/configure --prefix=/c/install_gdb  --with-expat
--- End code ---
5, make[press enter] , this will build the gdb.exe and gdbserver.exe, take about half an hour in my P43.0 CPU.
6, make install[press enter]

After this, all the files were in c:\install_gdb
Also, don't forget to run the strip command to reduce the file size in c:\install_gdb\bin

ollydbg:
I have upload the gdb7.0.1 version to gdb7.0.1_ollydbg.7z.

I  built it in TDM GCC 4.4.1dw2, also, I have comment the warning statement in symtab.c of the gdb source, so there is no such warning now. Since the new GDB 7.0.50 version and the GDB branch 7.0.90 is still experience the watch wxString lag problem I statement before.

Also, I build this gdb.exe statically link the expat library, so you don't need expat-1.dll.

ollydbg:
Hi, all.
today, gdb 7.1 official released, see here: GDB: The GNU Project Debugger

I have build this version under Loaden's GCC 4.4.3. I can debug under Codeblocks, but I still have some problems. the major problem is that showing variables in the Watch window of C::B, and the command interpreter runs really slow when I debug the Codecompletion plugin DLL.

See a more details in Asm_gmail - Re: gdb-7.1 - last call before release (Wed, Mar 17th).

Can some one help me? you can build a gdb yourself, or you can test the gdb I built from gdb7.1.7z

Thanks.

Edit
You can compare these two version of gdb
gdb7.0.1_ollydbg.7z, I build from TDM gcc 4.4.1dw2,with static expat library, based on the official gdb 7.0.1 source code, and I only comment out the #psymbal warning message.
and
gdb7.1.7z, I built from Loaden gcc 4.4.3, with static expat library, based on the official gdb 7.1 source code.

You will notice that the first one gdb7.0.1_ollydbg.7z runs really faster then the second one.

oBFusCATed:
Ah, great... time to test gdb_mi with this :)

Loaden:

--- Quote from: ollydbg on March 19, 2010, 04:01:03 am ---I have build this version under Loaden's GCC 4.4.3. I can debug under Codeblocks, but I still have some problems. the major problem is that showing variables in the Watch window of C::B, and the command interpreter runs really slow when I debug the Codecompletion plugin DLL.

--- End quote ---
In here, there is no delay, very fast! :lol:

Navigation

[0] Message Index

[#] Next page

[*] Previous page