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

[OT] unofficial MinGW GDB gdb with python released

<< < (18/35) > >>

ollydbg:
I find two place I can download the expat.

one is here, from mingw
http://sourceforge.net/projects/mingw/files/MinGW%20expat/expat-2.0.1-1/expat-2.0.1-1-mingw32-src.tar.gz/download

the other is here, from expat official site
http://sourceforge.net/projects/expat/files/expat/2.0.1/expat-2.0.1.tar.gz/download

Did I need to do this:
1, download expat
2, build expat, then it generate a static library like: expat.a
3, then I copy the expat.a to the mingw library folder, and I copy the expat's header files to mingw's include header folders.
4, Then, I build the gdb

right?

ironhead:

--- Quote from: ollydbg on February 27, 2010, 05:51:06 am ---I find two place I can download the expat.

one is here, from mingw
http://sourceforge.net/projects/mingw/files/MinGW%20expat/expat-2.0.1-1/expat-2.0.1-1-mingw32-src.tar.gz/download

the other is here, from expat official site
http://sourceforge.net/projects/expat/files/expat/2.0.1/expat-2.0.1.tar.gz/download
--- End quote ---

You can use either.  The MinGW sources are the same as the official sources, just renamed.


--- Quote ---Did I need to do this:
1, download expat
2, build expat, then it generate a static library like: expat.a
3, then I copy the expat.a to the mingw library folder, and I copy the expat's header files to mingw's include header folders.
4, Then, I build the gdb

right?
--- End quote ---

Correct.  You can statically link or dynamically against expat.  You can also add '-L<path to expat> -I<path to expat>' to your CFLAGS when compiling gdb.

ollydbg:
Thanks ironhead.

now, I have successfully build the expat library.

I use this command, suppose I would like to install to C:\ccc, in MSYS, in the expat source root


--- Code: ---./configure -prefix=/c/ccc --enable-shared  [enter]
...
make[enter]

make install [enter]


--- End code ---

Now, I have both dlls and headers and libraries in the C:\ccc

then I copy these files to MinGW, so, now, GCC can use these libraries.

Now, I use these command to configure GDB, suppose I'm in GDB source folder:

--- Code: ---configure -prefix=/c/ddd -enable-shared [enter]
...
make[enter]

make install [enter]

--- End code ---

I'm now building gdb.exe now. Am I right??? thanks.

I would like dynamiclly link to the utilitbins and expat-1.dll as you release 7.0.1. Thanks.

ollydbg:
I have successfully built the gdb.exe from snapshot of gdb-7.1.50.20100226, but when I'm checking it's dependency, it is *not* depend on the expat-1.dll. As a result, I can't debug CodeCompletion plugin, when I'm setting a breakpoint in the DLL source, the program didn't stopped at that point.

As I found from other site, it seems the expat library is necessary to debug Windows DLL files.

So, my question is: How to configure the GDB to let it depend on the expat.dll?

Edit:


--- Code: ---You can also add '-L<path to expat> -I<path to expat>' to your CFLAGS when compiling gdb.
--- End code ---
Since I have already copy the generated lib,headers to MinGW folder, do I still set the library path and include path?

I found in here: http://sourceware.org/ml/gdb/2010-01/msg00189.html
What does "-static" used for??

Edit2
In this page http://sourceware.org/gdb/current/onlinedocs/gdb/Requirements.html
Do I need add

--- Code: -----with-libexpat
--- End code ---
??

ollydbg:
Oh, I found that I used to do the configure in the root folder(which is totally wrong!!!.....), which is in

C:\gdb-7.1.50.20100226

But for correctly configuration, I need to "cd" to

C:\gdb-7.1.50.20100226\gdb

then ,run


--- Code: ---./configure --with-expat
--- End code ---

in this folder... :D

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version