You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's time to get Real Serious ™️ and add logging to goblin.
There are a number of places in goblin where things have "gone wrong", but not enough that we shouldn't parse.
Refactoring dyn to check the index of DT_NEEDED to fix a bug found while fuzzing, ref #27, we should continue parsing, but the client only receives a None, which is fine for clients, but we may also want to know why we received none, hence a warn! would be appropriate.
There are also many times when debugging, e.g., #28, I just need to see the execution state at the point of failure, which is precisely what debug! is for.
Steps
add extern log
add logs in various places, useful places. debug! for extremely verbose stuff, info maybe, and warn! where the binary is malformed some way, e.g., in first example.
add to PE
add to ELF
add to mach
The text was updated successfully, but these errors were encountered:
It's time to get Real Serious ™️ and add logging to goblin.
There are a number of places in goblin where things have "gone wrong", but not enough that we shouldn't parse.
Refactoring
dyn
to check the index ofDT_NEEDED
to fix a bug found while fuzzing, ref #27, we should continue parsing, but the client only receives aNone
, which is fine for clients, but we may also want to know why we received none, hence awarn!
would be appropriate.There are also many times when debugging, e.g., #28, I just need to see the execution state at the point of failure, which is precisely what
debug!
is for.Steps
extern log
debug!
for extremely verbose stuff,info
maybe, andwarn!
where the binary is malformed some way, e.g., in first example.The text was updated successfully, but these errors were encountered: