Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Segmentation fault in nativeparser.cpp

<< < (4/4)

ollydbg:

--- Quote from: oBFusCATed on March 16, 2013, 04:43:59 pm ---
--- Quote from: ollydbg on March 16, 2013, 10:28:13 am ---Then, I guess compiler destroyed before cc, so crash happens.

--- End quote ---
Probably you can add an event which notifies all plugins that the unload process has started, so they can clean themselves and they can untangle some of the dependencies.

--- End quote ---
I'm not fully understand this idea.
Do you mean, if cc received a "unload start" event, it will not call some function of compiler plugin?
Can you be more specific?
Thanks.

Grad:

--- Quote from: ollydbg on March 16, 2013, 10:28:13 am ---The crash happens like below steps(I guess):
1, app started
2, both cc and compiler plugin loaded correctly
3, user open a cbp project
4, cc start parsing (after some timer delay) and query compiler search path from compiler plugin(this internally call gcc command line)
5, user click the "close" button of the app

--- End quote ---

I had the same with older (slower) XP systems. The CC was using the log which wasn't there any more (at shutdown).
I have solved this with the appShutDown flag in OnRelease and use this same flag as argument in the ClearParsers.
In the deleteParser and RemoveProjectFromParser I use this flag to turn off the logging.

I had no problems since with shutting down.

(But the logging has nothing to do with compiler so that's strange).

ollydbg:

--- Quote from: Grad on March 18, 2013, 02:25:47 pm ---The CC was using the log which wasn't there any more (at shutdown).
I have solved this with the appShutDown flag in OnRelease and use this same flag as argument in the ClearParsers.
In the deleteParser and RemoveProjectFromParser I use this flag to turn off the logging.

I had no problems since with shutting down.

(But the logging has nothing to do with compiler so that's strange).

--- End quote ---
Can you show us the patches? Thanks.

@ALL:
About the logging in CC, why not use a wx standard log functions? It already supports messages from muti-threads.

Navigation

[0] Message Index

[*] Previous page