cc-branch crashes on linux

[MortenMacFly]

I personally think that not CC bug.
We need find the reason?

True - it's not as CC bug, but CC could avoid it.

[oBFusCATed]

Hm, Looks the same as the one in the debugger branch.
I think this should be fixed in C::B's sdk, not in every plugin, it will be easier I suppose

[killerbot]

but rather urgently ;-)

[Loaden]

but rather urgently ;-)

Fixed in CC.

[MortenMacFly]

I think this should be fixed in C::B's sdk, not in every plugin, it will be easier I suppose

True, If what I said is correct. As the loggers is an implementation of Thomas, I wonder what he believes is the right thing to do.

I would implement the destructor for the relevant loggers (including TextCtrlLogger) and set the control pointer to zero (NOT deleting it, as deletion will be done by the parent component in wxwidgets).

Any objections / thoughts / hints on that topic?!

[killerbot]

but rather urgently ;-)

Fixed in CC.

confirmed this fixes the issue.

[Loaden]

Hi, all!
I personally hope we can publish a CC BRANCH build in the "Nightly builds" board.
Because we need more extensive testing in order to perfect the CC.
Any comments?

[MortenMacFly]

confirmed this fixes the issue.

On second thoughts:
The loggers are one of the components destroyed at last. So in fact they should be valid during the shutdown/destruction of ANY plugin.

However, logging/UI access in operations called during shutdown (of plugins) should ALWAYS check if the app is shutting down -> just as Loaden did it in the patch for the CC branch. Basically that's what this method is for!

I have (however) attached a patch concerning the loggers for testing. It shouldn't harm but may introduce some "safety"... although it's not really a "good way".

I would welcome testing and feedback (@oBFusCATed: e.g. if this "fixes" the crash in the debugger branch).

I personally hope we can publish a CC BRANCH build in the "Nightly builds" board.

I had asked killerbot to do so, I'm afraid he didn't find the time or wanted to wait until the show-stoppers are solved.

[killerbot]

wanted to wait until the show-stoppers are solved.

But this weekend I will create one.

I could do all 3 of them :
regular
cc
debugger (if there are any updates ?)

[Loaden]

wanted to wait until the show-stoppers are solved.

But this weekend I will create one.

I could do all 3 of them :
regular
cc
debugger (if there are any updates ?)

Thanks a lot!

[ollydbg]

wanted to wait until the show-stoppers are solved.

But this weekend I will create one.

I could do all 3 of them :
regular
cc
debugger (if there are any updates ?)

Nice, glad to hear! thank you!!!

[oBFusCATed]

I would welcome testing and feedback (@oBFusCATed: e.g. if this "fixes" the crash in the debugger branch).

No, it doesn't, it's the same as before, the logger has control pointer pointing to the dead gui object...

Steps to reprocude:
1. start cb
2. start some app
3. attach to the app
4. close cb