Make implementation of LibsecretAttributesBuilder more robust |
|||||
Issue descriptionIn LibsecretAttributesBuilder, the internals of the name_values_ container are referenced by external objects. These references can break, depending on the implementation details of the container. For example, std::list works but std::vector fails the asan tests. We should provide the needed storage in an alternative way, such that the references don't depend on implementation details.
,
Jun 6 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23 2017
,
Oct 23
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23
This change is aesthetic for the code and won't have actual impact. Let's not expect that someone will invest time on this |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by vabr@chromium.org
, Jun 6 2016