Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

parser test rev 7157 error?

<< < (4/7) > >>

oBFusCATed:
ollydbg: on some OSes mutexes could be recursive.
You can do


--- Code: ---mutex.lock();
some code
mutex.lock();

some code
mutex.unlock();
mutex.unclock();

--- End code ---

This is not recommended, but it is possible. (http://docs.wxwidgets.org/stable/wx_wxmutex.html#wxmutex)

ollydbg:

--- Quote from: oBFusCATed on May 27, 2011, 11:49:14 am ---ollydbg: on some OSes mutexes could be recursive.
You can do


--- Code: ---mutex.lock();
some code
mutex.lock();

some code
mutex.unlock();
mutex.unclock();

--- End code ---

This is not recommended, but it is possible. (http://docs.wxwidgets.org/stable/wx_wxmutex.html#wxmutex)

--- End quote ---

Hi, thanks for the great explanation, I will look into it. I used to know that a critical section can only entered once. :D

ollydbg:

--- Quote from: Loaden on May 27, 2011, 11:13:47 am ---I'm removed the locker in my local commit (git-svn).
And commit them on tonight.

--- End quote ---
I see your latest commit.
As obf said, if the locker can entered several times, it can NOT "lock" any thing. :D, so they can be removed.

Loaden:

--- Quote from: ollydbg on May 27, 2011, 01:55:34 pm ---
--- Quote from: Loaden on May 27, 2011, 11:13:47 am ---I'm removed the locker in my local commit (git-svn).
And commit them on tonight.

--- End quote ---
I see your latest commit.
As obf said, if the locker can entered several times, it can NOT "lock" any thing. :D, so they can be removed.

--- End quote ---
But after remove the locker, there should have some issue.
i.g. When do CC search for call tips, and another batch parse is running.
Then, there is not thread safe.
In some where, we shoud add a locker.
But now, I have no idea.

ollydbg:
CC search for tip should only works when there is NO batch parsing.
Are there any state variable indicate that batch parsing is running?

Navigation

[0] Message Index

[#] Next page

[*] Previous page