Searched hist:"96 ad9069" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/google-ipmi-sys/ |
| H A D | handler_impl.hpp | 96ad9069 Tue Nov 24 23:47:20 CST 2020 William A. Kennington III <wak@google.com> Remove globally constructed variables
Using global variables that have construction order dependencies on each
other do not guarantee the expected execution order. We had an issue
where the defaultConfigPath is not constructed from the string in
handler.cpp before it was used to construct the Handler impl.
This resolves the issue by removing runtime constructed global variables
entirely.
Change-Id: I868f34782d22d3b2b07be303a05f58b9c9f8c8b8
Signed-off-by: William A. Kennington III <wak@google.com>
|
| H A D | main.cpp | 96ad9069 Tue Nov 24 23:47:20 CST 2020 William A. Kennington III <wak@google.com> Remove globally constructed variables
Using global variables that have construction order dependencies on each
other do not guarantee the expected execution order. We had an issue
where the defaultConfigPath is not constructed from the string in
handler.cpp before it was used to construct the Handler impl.
This resolves the issue by removing runtime constructed global variables
entirely.
Change-Id: I868f34782d22d3b2b07be303a05f58b9c9f8c8b8
Signed-off-by: William A. Kennington III <wak@google.com>
|
| H A D | handler.cpp | 96ad9069 Tue Nov 24 23:47:20 CST 2020 William A. Kennington III <wak@google.com> Remove globally constructed variables
Using global variables that have construction order dependencies on each
other do not guarantee the expected execution order. We had an issue
where the defaultConfigPath is not constructed from the string in
handler.cpp before it was used to construct the Handler impl.
This resolves the issue by removing runtime constructed global variables
entirely.
Change-Id: I868f34782d22d3b2b07be303a05f58b9c9f8c8b8
Signed-off-by: William A. Kennington III <wak@google.com>
|