std::list .size method

I have seen sometimes core files in my application and when I bactraced I found it is coring at executing .size() function on std::list

std::list<std::string> myStringList

myStringList.size() sometimes cores

myStringList is member of static class which has only one instance for the entire application. I understand it should be protected by lock which I am not doing but could .size() on list ever core?
learningunixAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Infinity08Commented:
Many things can cause a core dump given the right (or better : wrong) set of circumstances.

What kind of core dump is it ?

Is there a possibility of memory corruption ?

Since you mentioned locking, are multiple threads trying to access the list ?
0
learningunixAuthor Commented:
I was looking more into the code, I was having lock when I add entry to the list but when retrieving the size() I don't lock it. Could this cause the core?

Based on my design, yes it is possible one thread can update the list while I am trying to retrieve the size() of the list by other thread

Here's what I see when it execute size() on the list.

Program terminated with signal 11, Segmentation fault.
#0  0x00007f219fff95b1 in std::_List_const_iterator<string*>::operator++ (this=0x7f21ab5e8f58) at /usr/include/c++/4.3/bits/stl_list.h:221
221             _M_node = _M_node->_M_next;
(gdb) bt
#0  0x00007f219fff95b1 in std::_List_const_iterator<string*>::operator++ (this=0x7f21ab5e8f58) at /usr/include/c++/4.3/bits/stl_list.h:221
#1  0x00007f219fff95e4 in std::__distance<std::_List_const_iterator<string*> > (__first=..., __last=...) at /usr/include/c++/4.3/bits/stl_iterator_base_funcs.h:84
#2  0x00007f219fff962d in std::distance<std::_List_const_iterator<string*> > (__first=..., __last=...) at /usr/include/c++/4.3/bits/stl_iterator_base_funcs.h:119
0
Infinity08Commented:
>> it is possible one thread can update the list while I am trying to retrieve the size() of the list by other thread

Then that's a big suspect :)

You will need some way of ensuring this doesn't happen, and proper locking is one such way.
0
Angular Fundamentals

Learn the fundamentals of Angular 2, a JavaScript framework for developing dynamic single page applications.

learningunixAuthor Commented:
hmmm... I thought executing .size() on list is just a passive command and this should be ok. looks like my assumption is wrong
0
Infinity08Commented:
A std::list is a linked list. Calculating the size of a linked list is not "passive", but involves traversing all nodes in the list.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
learningunixAuthor Commented:
Thanks a lot.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C++

From novice to tech pro — start learning today.