Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Custom Watch Script Pluggins

<< < (7/10) > >>

thomas:

--- Quote from: Game_Ender on January 25, 2006, 11:45:25 pm ---
--- Quote from: thomas on January 25, 2006, 11:20:46 pm ---I have the feeling the debugger is getting terribly slow... someone should optimize it.

--- End quote ---

I going to take one of these dangerous stabs in the dark, but does having to comunicate over stdin/stdout put an upper limit on performance?  Is that our current bottleneck?

--- End quote ---
For heaven's sake! Don't tempt him any further, or he'll really start off! :lol:

rickg22:
has somebody tried to profile codeblocks while debugging a program?

Game_Ender:
I have had the worst time profiling a shared library.  I have gotten as far as generating libdebuggergdb.so.profile .  But I am sure I need a tool called "sprof" to get the actual profile graph.  But I can't find it anywhere.  In other notes the Main Code::Blocks app spends about 30-40% of its time processing events.

EDIT- I found sprof, it was in the libstdc-prof package, but It comes back with a very small mangled named graph.  On windows you could try using AMD Code Analyzer.

mandrav:
How does this look?


--- Code: (cpp) ---// Registers new types with driver
void RegisterTypes(DebuggerDriver@ driver)
{
    driver.RegisterType(
        // The type's name (must be unique, the debugger driver won't accept duplicates).
        "STL String",
        // Regular expression for type matching.
        "[^[:alnum:]_]*string[^[:alnum:]_]*",
        // Evaluate function's name (defined below).
        "Evaluate_StlString",
        // Parser function's name (defined below).
        "Parse_StlString"
    );
}

// This function tells the driver how to evaluate this type.
// a_str contains the variable and result must contain the debugger's command when it returns.
void Evaluate_StlString(const wxString& in a_str, wxString& out result)
{
    result = "output " + a_str + ".c_str()";
}

// This function parses driver's output.
// When it returns, the "result" argument contains the parsing result.
void Parse_StlString(const wxString& in a_str, wxString& out result)
{
    // nothing needs to be done
    result = a_str;
}

--- End code ---

Game_Ender:
That is very cool, awesome job Mandrav.  That looks like it is clean and should be pretty independent.  But like mentioned above, when you are doing some complicated like STL vectors and such you might have to use library specific names, is there some way to for script to detect what compiler you are using so it can react accordingly?

Navigation

[0] Message Index

[#] Next page

[*] Previous page