Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
Clang CC
l_inc:
Alpha
You can attach to the running CB when it's already frozen and at least to lookup the call stacks.
Alpha:
Thanks. Turns out it was the debug printing attempting send to the console when C::B was started full GUI mode that caused the freeze. (Starting C::B inside a terminal works just fine.)
yvesdm3000:
Pretty interesting, I always run it from the terminal to get the debugging output... Glad to see you're up and running again. Maybe we should move the debug-output to a macro or something.
I'm currently tackling the TokenDatabase to span the whole project/workspace with persistence ondisk. This is needed for useful 'go to implementation' and most refactoring operations. For normal Code-completion this is not really necessary, but some results-filtering is currently still disabled because I don't want to make it another thread-context-switch, I think it should be done in the same flow where code-completion was requested. It's not hard, but I don't really miss it myself.
Yves
Jenna:
Why not use the logmanager ?
--- Code: (cpp) ---Manager::Get()->GetLogManager()->DebugLog(F(_("")));
--- End code ---
or
--- Code: (cpp) ---Manager::Get()->GetLogManager()->DebugLogError(F(_("")));
--- End code ---
This logs to debug-log if available and/or to console (if open).
yvesdm3000:
Is it threadsafe ?
Yves
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version