|
ollydbg
|
 |
« Reply #60 on: January 13, 2010, 06:32:01 am » |
|
Just a reminder: In the MinGW mail list: one problem still exist. too many gdb warning when debugging C::B |
|
|
|
|
Logged
|
Note: I'm not the author of Ollydbg debugger! Never ask question about that.
|
|
|
|
ollydbg
|
|
« Reply #61 on: January 13, 2010, 06:59:14 am » |
|
To reproduce this bug. you can do like this:
1, open codeblocks.cbp in C::B.
2, build the whole project.
3, place a break point in the line 488 of MainFrame::MainFrame() function (in file: F:\cb_svn\src\src\main.cpp)
4. press the "debug" button on the toolbar.
5, when the debugger hit the breakpoint, you need to open the "call stack" dialog.
6, from the "debug log" panel, you can see a lot of warnings.(You need to select: Menu->settings->Compiler and debugger settings-> debugger settings. and select "display debugger's log).
Any comments or suggestions? thanks.
|
|
|
|
|
Logged
|
Note: I'm not the author of Ollydbg debugger! Never ask question about that.
|
|
|
|
|
Biplab
Scripts wizard
Lives here!
Posts: 1604
|
|
« Reply #63 on: February 07, 2010, 05:16:06 pm » |
|
Thanks Chris. I've been using it since you made this announcement in MinGW mailing list. This build is much better than previous gdb 7 versions.  |
|
|
|
|
Logged
|
Be a part of the solution, not a part of the problem.
|
|
|
|
oBFusCATed
|
|
« Reply #64 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?
|
|
|
|
|
Logged
|
|
|
|
ironhead
Advanced newcomer
Posts: 119
|
|
« Reply #65 on: February 08, 2010, 02:10:33 am » |
|
ironhead:
Does this release has python scripting enabled?
If it is not enabled can you tell me why?
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. |
|
|
|
|
Logged
|
|
|
|
|
ollydbg
|
|
« Reply #66 on: February 08, 2010, 07:58:55 am » |
|
thanks chris for your hard work. I will tested tonight. EditIt works fine, and the symtab/psymtab bug is fixed. Thanks very much!! |
|
|
|
« Last Edit: February 08, 2010, 02:27:28 pm by ollydbg »
|
Logged
|
Note: I'm not the author of Ollydbg debugger! Never ask question about that.
|
|
|
JZ
Newcomer
Posts: 1
|
|
« Reply #67 on: February 09, 2010, 06:02:45 am » |
|
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?
|
|
|
|
« Last Edit: February 09, 2010, 06:15:16 am by JZ »
|
Logged
|
|
|
|
|
jens
|
|
« Reply #68 on: February 09, 2010, 10:12:59 am » |
|
Do I need to separately install GDB?
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" . |
|
|
|
|
Logged
|
|
|
|
|
ollydbg
|
|
« Reply #69 on: February 11, 2010, 03:33:38 pm » |
|
@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. > 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:
When the codeblocks send the command : output xxxxx to gdb, it takes several (more than 10s) to return the string value. |
|
|
|
|
Logged
|
Note: I'm not the author of Ollydbg debugger! Never ask question about that.
|
|
|
|
jens
|
|
« Reply #70 on: February 11, 2010, 07:55:55 pm » |
|
@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. > 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:
When the codeblocks send the command : output xxxxx to gdb, it takes several (more than 10s) to return the string value. What happens, if you debug from commandline ? |
|
|
|
|
Logged
|
|
|
|
|
jens
|
|
« Reply #71 on: February 11, 2010, 08:29:35 pm » |
|
What happens, if you debug from commandline ?
Or if you put the command in the "Command:" text-control and execute it (without running of C::B's gdb-parser) ? Do you use any debugger related patches or clean sources from trunk. I just tested it with gdb 7.0.50 as cross-debugger for a wxMSW app on my linux-box and the output occurs immediately after the command is sent to gdb (from inside the program or from the textcontrol). |
|
|
|
|
Logged
|
|
|
|
|
jens
|
|
« Reply #72 on: February 11, 2010, 08:32:56 pm » |
|
One more question: what do you try to debug ?
I switched to gdb 6.80 on my linux-box, because all 7.0 versions do not work correctly with parts of the C::B sources (at least not when compiled with wxWidgets debug version), 6.80 works fine.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
ollydbg
|
|
« Reply #74 on: February 12, 2010, 12:47:59 am » |
|
Ok, gdb 7 works fine when I debug a simple wxWdigets created from the "project wizard" in Codeblocks, there's no time lag here.
So, the problem is, it works badly when I'm debugging some C::B's source.
|
|
|
|
|
Logged
|
Note: I'm not the author of Ollydbg debugger! Never ask question about that.
|
|
|
|
