Project

General

Profile

Bug #16113

Support #16096: Fix problems found when attempting to build with gcc 6.3.0

ProviderList test fails in larcore

Added by Gianluca Petrillo over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Library
Target version:
-
Start date:
04/05/2017
Due date:
% Done:

100%

Estimated time:
Spent time:
Occurs In:
Experiment:
-
Co-Assignees:
Duration:

Description

Tested with debug qualifiers, the test ends in a segmentation fault.

Associated revisions

Revision b085ce12 (diff)
Added by Gianluca Petrillo over 3 years ago

Fixed bug on erase of items from a provider list.

It turns out that std::unordered_map::erase() invalidates the iterator
it is erasing, which makes some sense.
This should solve issue #16113.

Revision fd59ea4a (diff)
Added by Gianluca Petrillo over 3 years ago

Fixed bug on erase of items from a provider list.

It turns out that std::unordered_map::erase() invalidates the iterator
it is erasing, which makes some sense.
This should solve issue #16113.

Revision 7fea2977 (diff)
Added by Gianluca Petrillo over 3 years ago

Fixed bug on erase of items from a provider list.

It turns out that std::unordered_map::erase() invalidates the iterator
it is erasing, which makes some sense.
This should solve issue #16113.

Revision 3ec0f9e0 (diff)
Added by Gianluca Petrillo over 3 years ago

Fixed bug on erase of items from a provider list.

It turns out that std::unordered_map::erase() invalidates the iterator
it is erasing, which makes some sense.
This should solve issue #16113.

History

#1 Updated by Gianluca Petrillo over 3 years ago

  • Status changed from New to Assigned

#2 Updated by Gianluca Petrillo over 3 years ago

The method std::unordered_map::erase, called on an iterator, invalidates that iterator.
I was using that same iterator to find out the next element, which obviously fails.

Fixed by larcore:b085ce12777120e08164a5004d2501eed595499f .

#3 Updated by Gianluca Petrillo over 3 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

#4 Updated by Gianluca Petrillo over 3 years ago

  • Description updated (diff)

#5 Updated by Lynn Garren over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF