Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
MortenMacFly:
--- Quote from: oBFusCATed on November 25, 2010, 10:30:47 pm ---Running HEAD of the branch and I can start and use C::B, even the disassembly window works.
--- End quote ---
Well - the strange thing is: If I disable the debugger plugin all works fine again. All editors (based on wxScintilla) are able to create their windows, just not the disassembly window. This error remains which makes the debugger plugin unusable for me atm. :-(
--- Quote from: oBFusCATed on November 25, 2010, 10:30:47 pm ---Which logs?
--- End quote ---
The SVN diff I meant, not log.
--- Quote from: oBFusCATed on November 25, 2010, 10:30:47 pm ---Morten, you can find code like "SomeManager *manager = Manager::Get()->GetSomeManager();" all over C::B's sources and very few times the pointer is checked.
--- End quote ---
That is exactly what I meant! This version is the standard and it's OK to use this even without pointer check (as I've written:)
--- Quote from: MortenMacFly on November 25, 2010, 08:54:15 pm ---The only exception might be singleton classes, but even then you must be careful if the app shuts down.
--- End quote ---
All I am asking for is to use the same style everywhere, so use the managers as pointers (SomeManager *manager =...) and not as reference (SomeManager &manager =...), that's it.
--- Quote from: MortenMacFly on November 25, 2010, 08:54:15 pm ---If you don't like it, you can rewrite it the style you prefer :)
--- End quote ---
I can do so. But please keep the "correct" style in mind in the future just for consistency (not functionality).
oBFusCATed:
--- Quote from: MortenMacFly on November 26, 2010, 06:36:06 am ---
--- Quote from: oBFusCATed on November 25, 2010, 10:30:47 pm ---Running HEAD of the branch and I can start and use C::B, even the disassembly window works.
--- End quote ---
Well - the strange thing is: If I disable the debugger plugin all works fine again. All editors (based on wxScintilla) are able to create their windows, just not the disassembly window. This error remains which makes the debugger plugin unusable for me atm. :-(
--- End quote ---
Stupid questions: have you tried full rebuild or checkout of a clean version in another directory?
Anyone else having the same problems?
--- Quote from: MortenMacFly on November 26, 2010, 06:36:06 am ---I can do so. But please keep the "correct" style in mind in the future just for consistency (not functionality).
--- End quote ---
Okay :)
MortenMacFly:
--- Quote from: oBFusCATed on November 26, 2010, 09:59:43 am ---Stupid questions: have you tried full rebuild or checkout of a clean version in another directory?
--- End quote ---
Yes, several times, different machines. On all machines I have the same effect (they all have a common OS though...).
--- Quote from: MortenMacFly on November 26, 2010, 06:36:06 am ---Anyone else having the same problems?
--- End quote ---
I would be interested in this very much, too. I'll try to compile the debugger version only (thus not having applied my local modification of wxScintilla). Still I believe that is not the reason as wxScintilla works well in all other editors / plugins (e.g. cbEditor, the preview in ThreadSearch and alike...).
Maybe Lieven can give some hints when compiling another nightly of the branch... at any time.
killerbot:
I had plan to build a new version somewhere either Sunday morning, or Sunday evening.
Since trunk has been merged to debugger_branch, it is a good time indeed ...
PS : something that occurs to me from time to time on trunk while debugging :
CB stops the debug sessions (or the debug sessions was stopped because the program ran till completion), nevertheless CB keeps showing that the debugger is still running (and it is actually, asking through CB [toolbar- button or menu] to stop doesn't help). Only solution is to kill gdb, and then we are back in bizznizz.
Oh yeah : on linux.
oBFusCATed:
killerbot:
Can you try the branch to see if this behavior happens there, too?
I think, I've seen this in the past with trunk's version, the branch's version doesn't have this problem or I've not seen it lately (unfortunately I'm not using C::B much).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version