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

[OT] unofficial MinGW GDB gdb with python released

<< < (6/35) > >>

theOcelot:

--- Quote from: oBFusCATed on October 09, 2009, 07:54:10 pm ---Can you try a nightly build?

--- End quote ---
Who, me? Of CB? Sure, I guess. Do you mean get it from SVN? I can't find a binary download link for the nightlies anymore. I also don't know for sure how the build will work with my wxWidgets.

oBFusCATed:
theOcelot: yes you  :lol:,  binary nightly build (not hyper new, but uber new relative to the 8.02 release) can be found in the nightly subforum on this site  :lol:

ollydbg:
@theOcelot

I test your code.

Q:Is breakpoint in a header file works?

A: Win XP TDM-MinGW 4.4.1  GDB 6.8.3 works

A: Win XP TDM-MinGW 4.4.1  GDB 7.0    works


By the way:
Does other guys try setting a breakpoint in a C::B's plugin source, like plugins\codecompletion\parser\tokenizer.cpp. It seems the breakpoints don't work there. The problem is quite the same:


--- Code: --->>>>>>cb_gdb:
> break "F:/cb_svn/src/plugins/codecompletion/parser/tokenizer.cpp:591"
No source file named F:/cb_svn/src/plugins/codecompletion/parser/tokenizer.cpp.
Breakpoint 4 ("F:/cb_svn/src/plugins/codecompletion/parser/tokenizer.cpp:591) pending.
--- End code ---

theOcelot:
Ha! Victory! I hand-compiled main.cpp into main.o on the command line, using relative paths with forward slashes instead of absolute paths with backslashes, as in Bob Fletcher's bug report. Once CB linked it, it worked, and all three header breakpoints were hit.

The nightly build has the same behavior, passing paths using backslashes, so the problem didn't go away when I switched. Maybe it will let me ctrl-shift-F9 to compile just one file without crashing again, in which case it will have been worth it anyway.

ollydbg:
I think I find the reason why I can't debug C::B under GDB 7.0 (Win XP TDM-MinGW 4.4.1 )

Here is my steps:
1, clear all the breakpoints.
2, I start debugging.
3, the debuggee started
4, but I fond that GDB.exe hungs, because I can't manually send the debug command in the "debug" panel. There's no response after I hit enter button.

 :(

Any ideas?

Edit
I just do another test:

1, clear all the breakpoints.
2, I start debugging.
3, the debuggee started
4, I click on the "stop debugger" button, but it seems the debugger can't be paused.

Here is the log:


--- Code: ---Debugger name and version: GNU gdb (GDB) 7.0
Trying to pause the running process...

--- End code ---

So, I know why I can't set breakpoint when debugging, you can see the code below:


--- Code: ---bool DebuggerGDB::AddBreakpoint(const wxString& file, int line)
{
    const bool debuggerIsRunning = !IsStopped();
    if (debuggerIsRunning)
    {
        Break();
    }
    m_State.AddBreakpoint(file, line, false);
    if (m_pBreakpointsWindow)
    {
        m_pBreakpointsWindow->Refresh();
    }
    if (debuggerIsRunning)
    {
        Continue();
    }
    return true;
} // end of AddBreakpoint

--- End code ---

But it seems the "Break();"  function can not be executed correctly( gdb is still running or gdb hangs ), then certainly I can't set the following breakpoints.

Navigation

[0] Message Index

[#] Next page

[*] Previous page