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

crash on close cbp project (rev 7773)

<< < (2/6) > >>

ollydbg:

--- Quote from: jens on February 05, 2012, 01:25:19 pm ---I hope it's finally fixed with svn r7777 (with this revision-number it must be fixed  ;) ).

Additionally closing large projects should be much faster.
My very large test-project (linux kernel 2.6.35 with more than 30000 files) closes about 4 times faster (1200 ms instead of almost 5000 ms).
Times are measured without codecompletion-plugin, which is a little bit unstable at the moment.

--- End quote ---
Hi, jens, I can confirm that open/close the cbp project does not crash again. Thank you!

MortenMacFly:

--- Quote from: jens on February 05, 2012, 01:25:19 pm ---Times are measured without codecompletion-plugin, which is a little bit unstable at the moment.

--- End quote ---
It shouldn't be any longer. If it is, please report. I have concluded the things I wanted to change. The next change will take some more time...

oBFusCATed:
Is there any particular reason to remove the ';' after the locking macros? It looks pretty weird.

I'll give it a try in a minute and I'll report if there are any crashes.

ollydbg:

--- Quote from: oBFusCATed on February 05, 2012, 03:47:35 pm ---Is there any particular reason to remove the ';' after the locking macros? It looks pretty weird.

--- End quote ---
One reason I can say is: It will make our cc's parser happy(they like a function call statement) ;).

MortenMacFly:

--- Quote from: oBFusCATed on February 05, 2012, 03:47:35 pm ---Is there any particular reason to remove the ';' after the locking macros? It looks pretty weird.

--- End quote ---
Yes, because if you set the macros to nothing, they will expand to truly nothing. Otherwise they would expand to a semicolon. the latter I believe is "more weird". ;-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page