Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
They look like wx ones, probably wx calls OutputDebugString or something like that. Can you try to disable the debugging of wxwidgets?
MortenMacFly:
--- Quote from: oBFusCATed on January 29, 2012, 02:53:27 pm ---They look like wx ones, probably wx calls OutputDebugString or something like that. Can you try to disable the debugging of wxwidgets?
--- End quote ---
How do I do that? You mean *not* using --verbose? I am using the release version of the wxWidgets library btw...
oBFusCATed:
I'm not really sure, but in 2.9+ they've change the debugging stuff for wx, probably you should check their docs, how to enable/disable debugging.
MortenMacFly:
--- Quote from: MortenMacFly on January 29, 2012, 05:21:51 pm ---How do I do that? You mean *not* using --verbose? I am using the release version of the wxWidgets library btw...
--- End quote ---
OK, I tried not using --verbose.
Now I get tons of messages like:
[debug]warning: ../../src/common/menucmn.cpp(976): assert "item" failed in Enable(): attempt to enable an item which doesn't exist
That's basically the error I am after. However, the freeze just encounters later and I cannot make this stupid message stop, because it's created permanently on every UpdateUI loop. So this is not a solution. It basically does not allow me to debug C::B using C::B. :-(
oBFusCATed:
Take a look here: http://docs.wxwidgets.org/2.9.3/overview_debugging.html
You can try to set wxDEBUG_LEVEL==0 or provide a null assert handler.
If this doesn't help, you can try to skip the warning line in the GDB_driver::ParseOutput
Put something like this
--- Code: ---if (line[i].StartsWith(wxT("warning:"))
{
m_pDBG->Log(wxT("skipped:")+lines[i]);
}
--- End code ---
before the "else if (lines.StartsWith(_T("Error ")) ||" line
I've not tried the code, so it might cause problems.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version