boost ptr_list serious problem

[davidmahorse@…]

I have defined a struct like below: there is a mutex in it. I just found this mutex cannot cross-thread,strang? But stl c++ list works well. It doesn't have such a strange problem. struct { ..... ptr_list<SeppContext> freeContextList; } when i invoke freeContextList.mutex1, I try:

freeContextList.mutex1.lock();

then a boost lock error jumped up. It is not my codes'problem. It is the problem of ptr_list of boost. strange?

[Marshall Clow]

Can you post a complete code example, please?

Something that we can try to compile?

[davidmahorse@…]

Replying to marshall:

Can you post a complete code example, please?

Something that we can try to compile?

I cannot upload my source.It is too big even if after I make clean. I have tested today. It is still a problem. If you want talk me in detail. You can join me in MSN my msn is: david_mahorse@… I could send my full source to you by pidgin of ubuntu 10.04.

[viboes]

Please could you clarify what is the context and the error?

[davidmahorse@…]

struct SeppContext { .....

mutex lockForSingleContext;mutex is a stand version of boost.

..... }

class sepp { .... list<SeppContext*> freeContextList; this stl list works fine ptr_list<SeppContext> freeContextList;this doesn't work ,it cannot crossthread such as epoll linux kernel }

I was trying to test my codes to handle exception: so I deliberately throw an exception in one function invoked by epoll threads which I defined. This exception is created by this sentence like that: ... scoped_array<char> pa(new char[0x7fffffff]); .... then I just didn't know there is a problem with ptr_list of boost. I just get strange exception of "boost lock" captured by my threads. At this time ,this point of "SeppContext" has entered in linux kernel of epoll and comes out. I traced where this exception comes from, then I find : .... pContext = freeContextList.back(); freeContextList.pop_back(); pContext->lockForSingleContext.lock();this sentence throws boost lock exception .... But I have found this point of pContext is good. The address of pContext is not changed by kernel of linux. But I can invoke other variable of this pContext. But I cannot invoke the mutex of lockForSingleContext in SeppContext. If I invoke then a boost lock exception jumps out. I have't use static_cast such things. Because I only have one process,but it is mult-threaded. And if I don't use ptr_list of boost, I find std list works fine. It doesn't throw boost lock exception. So I judge this is not the problem of my codes. It is the problem of boost ptr_list. I just found another serious problem of ip:tcp:socket. The socket handle in it cannot cross-thread. The problem is I cannot delete point of ip:tcp:socket to release socket handle. This point of ip:tcp:socket is also defined in SeppContext. It is not the problem of my codes. It is the problem of ASIO of boost.Trust me. I don't use ASIO now. I just use BSD socket raw functions. It works fine. All my environment is multi-threads and epoll things. Because I am doing basic network programming.

[davidmahorse@…]

Why don't you join me in google talk to know detail of it? My gmail and account of google of talk is: davidmahorse@…