xzvno
getChange
(osquery/core/watcher.cpp), change
is uninitialized if tryTo
throws an exception. And change.footprint
is assigned to state.initial_footprint
. Does it matter?seph
change
is declared and it’s various members worked with. Are you referring to change.footprint
specifically?tryTo
. Is that a method that can raise? I think it’s not supposed to raise. and instead return an error that takeOr
works withxzvno
tryTo
. It may be at
or takeOr
. Anyway, I mean if something is thrown, do we need to initialize change
in the catch block?seph
change
is declared outside it.
So if the members of that stuct are intialized as 0 when declared it seems fine. If they're undef it'd be bad. But I can't tell which is which. xzvno
seph
xzvno
change
when it is declared (or in the catch block). Should I ask it here or open an issue?seph
xzvno
seph