Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Release 16.01 for Mac
oBFusCATed:
If the backtrace is correct the crash has happened, because the editor has lost the focus while the tooltip is still being created.
Which leads to the tooltip being destroyed in an unexpected time.
Easior Lars:
--- Quote from: oBFusCATed on February 14, 2016, 11:49:37 am ---Does it happen every time or is it just some random event?
--- End quote ---
It happened while mouse scrolling in CB editor with some source codes.
--- Quote from: oBFusCATed ---You can try to start cb under lldb/gdb and wait for the crash to happen.
Then inspect the variables.
The line numbers in the crash report are totally wrong (the last character is removed).
--- End quote ---
Thanks. lldb is used by me this time to debug and it gives some information as follow:
--- Code: (bash) ---Process 62378 stopped
* thread #1: tid = 0x7770f, 0x0000000101f9025d libcodeblocks.dylib`Window::Destroy(this=0x0000000110f2ed90) + 61 at PlatWX.cpp:764, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x0000000101f9025d libcodeblocks.dylib`Window::Destroy(this=0x0000000110f2ed90) + 61 at PlatWX.cpp:764
761 {
762 if (wid) {
763 Show(false);
-> 764 GETWIN(wid)->Destroy();
765 }
766 wid = 0;
767 }
(lldb)
--- End code ---
Any suggestion?
oBFusCATed:
--- Quote from: Easior Lars on February 14, 2016, 12:24:04 pm ---Any suggestion?
--- End quote ---
Am I correct in my guess that the calltip is cancelled while it is being created?
Probably you can add a flag that marks the beginning/end of the calltip creation and then don't call the cancel function if this flag is set.
Or find out why the creation or cancellation is happening.
Easior Lars:
--- Quote from: oBFusCATed on February 14, 2016, 12:59:22 pm ---Am I correct in my guess that the calltip is cancelled while it is being created?
--- End quote ---
I don't know whether you are correct or not since I'm not familiar with the CB sources.
--- Quote from: oBFusCATed ---Probably you can add a flag that marks the beginning/end of the calltip creation and then don't call the cancel function if this flag is set.
--- End quote ---
How to add a flag? Do you mean that setting a breakpoint in lldb to debug CB?
oBFusCATed:
--- Quote from: Easior Lars on February 14, 2016, 01:18:08 pm ---I don't know whether you are correct or not since I'm not familiar with the CB sources.
--- End quote ---
Just inspect the backtrace. The name of the function on it will reveal what is going on.
--- Quote from: Easior Lars on February 14, 2016, 01:18:08 pm ---How to add a flag? Do you mean that setting a breakpoint in lldb to debug CB?
--- End quote ---
Modify the source by adding a bool flag then when you start the method that creates the calltip set it to true, when the method exits set it to false. Lastly add a check if the flag is set in the onkillfocus method.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version