User forums > General (but related to Code::Blocks)
[OT] unofficial MinGW GDB gdb with python released
ironhead:
--- Quote from: oBFusCATed on February 07, 2010, 06:52:20 pm ---ironhead:
Does this release has python scripting enabled?
If it is not enabled can you tell me why?
--- End quote ---
Python scripting is not enabled. To be honest I haven't looked in to adding it (I don't use it myself), but I'll take a look at what's involved in adding the support this coming week.
ollydbg:
thanks chris for your hard work. I will tested tonight.
Edit
It works fine, and the symtab/psymtab bug is fixed. Thanks very much!!
--- Quote from: ironhead on February 07, 2010, 03:16:07 pm ---Hi All,
Just a heads up, I've release a new GDB snapshot:
http://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/GDB-7.0.50.20100202/gdb-7.0.50.20100202-mingw32-bin.tar.gz/download
This release includes a fix for the symtab / psymtab warnings that will be part of the GDB 7.1 release when it becomes official.
Cheers!
Chris
--- End quote ---
JZ:
I'm trying to run the GDB debugger for on a Windows platform the first time on a C program and I get the following error message.
"The debugger executable is not set. To set it, go to "Settings/Compiler and debugger", switch to the "Programs" tab, and select the debugger program."
I looked on the Settings page and don't see a "Programs" tab. What am I missing?
Do I need to separately install GDB? If so, is there a how to link or can someone point me in the right direction?
Jenna:
--- Quote from: JZ on February 09, 2010, 06:02:45 am ---Do I need to separately install GDB?
--- End quote ---
Depends on your gcc installation.
But with this error-message the answer is most likely yes.
For a download see the link in one of the previous posts.
To check whether it is set up correctly, look into "Settings -> Compiler and debugger -> Global compiler settings -> [your compiler] -> Toolchain executables" .
ollydbg:
@Chris Sutcliffe
I find the 7.0.50 version of gdb didn't work correctly.
when I try to view a wxString value in Codeblocks, it takes a lot of time.
--- Code: ---> whatis m_Buffer
type = wxString
>>>>>>cb_gdb:
> output /c m_Buffer.m_pchData[0]@((wxStringData*)m_Buffer.m_pchData - 1)->nDataLength
{116 't', 101 'e', 115 's', 116 't', 46 '.', 99 'c', 112 'p', 112 'p'}>>>>>>cb_gdb:
--- End code ---
When the codeblocks send the command : output xxxxx to gdb, it takes several (more than 10s) to return the string value.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version