User forums > General (but related to Code::Blocks)
[OT] unofficial MinGW GDB gdb with python released
ironhead:
--- Quote from: ollydbg on February 23, 2010, 07:27:59 am ---Did you know whether there is a slow down when parsing the command input??? or there are other bugs? How can I report this bug?
--- End quote ---
I'm not sure if the slowdown is expected or not. I recommend following up on the gdb mailing list:
http://www.gnu.org/software/gdb/mailing-lists/
The gdb devs are normally pretty quick to respond.
ollydbg:
@ironhead:
Thanks, I posted a message in gdb maillist, also a bug report in the GDB Bugzilla.
ollydbg:
@iron
Today, I found that the time delay problem may due to the Compiler conflict. I used to use TDM-GCC 4.4.1 SIJI version.
Today, I downloaded the GCC 4.4.3 compiler from Loaden's google code:
http://code.google.com/p/qp-gcc
Then, I built wxWidgets library and Codeblocks_SVN using GCC 4.4.3, and try to debug my own "parserTest" project.
Unluckily, I encountered the problem like:
--- Quote ---This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
--- End quote ---
Both the official mingw gdb 7.0.1 and 7.0.50 get the same error.
Luckily, I found that I can debug the "parserTest" project by gdb.exe built from the latest gdb snapshot like: current/gdb-7.1.50.20100223
Also, it showed the wxString's value quickly, and there's no time lag.
So, if someone meet these same problem as me, I can upload the self built gdb.exe.
Edit
The self-build GDB.exe still has some problems...., and the CLI response time is still a bit slower then the official 7.0.1 :(
ollydbg:
@ironhead
I have another question:
I build the gdb in a very simple steps:
1, download the GDB tarball from the sourceware ftp
2, (I have MSYS and MinGW installed), I just swith to the GDBXXXX.XXX folder in MSYS command line
3, entering this command: configure
4, entering this command: make
So, my question is: it seems the previous version of gdb your build(offical mingw 7.0.1) was depend on the libexpat library. So, do I need to enable the expat library option?, if Yes, How can I build gdb depend on libexpat? thanks very much!
ironhead:
--- Quote from: ollydbg on February 27, 2010, 04:27:26 am ---So, my question is: it seems the previous version of gdb your build(offical mingw 7.0.1) was depend on the libexpat library. So, do I need to enable the expat library option?, if Yes, How can I build gdb depend on libexpat? thanks very much!
--- End quote ---
Yes, expat is required in order to debug DLLs (amongst other things). In order to build a gdb that uses expat, you would need to build expat itself (http://expat.sourceforge.net/) and place the headers / libraries somewhere that your compiler can find them.
The expat I use is available on the MinGW project page, but since you are using a different GCC, you will need to build it yourself. Thankfully the build process is pretty simple, just configure / make.
If you run in to any snags, let me know and I'll do my best to help you out.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version