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
One use case that @artemdinaburg raised was that he'd like to be able to introduce symbols into an existing program execution. Right now DeepState is very unit test focused -- i.e. run to DeepState_Run, then change control to one of the unit test case entry-points. Ideally we'd like to be able to treat the "rest of the program" as the test case, and basically get to use the DeepState API.
This means changing DeepState's behaviour slighty:
If execution reaches DeepState_Run, then it will go and look for all the test cases.
If execution reaches DeepState_TakeOver then we add some fake TestInfo structure (or maybe DeepState_TakeOver is a macro that calls a lower level function and passes in an initialized struct DeepState_TestInfo), then return 1 when under symbolic execution (by being hooked) and 0 by default in a native execution.
The text was updated successfully, but these errors were encountered:
One use case that @artemdinaburg raised was that he'd like to be able to introduce symbols into an existing program execution. Right now DeepState is very unit test focused -- i.e. run to
DeepState_Run
, then change control to one of the unit test case entry-points. Ideally we'd like to be able to treat the "rest of the program" as the test case, and basically get to use the DeepState API.This means changing DeepState's behaviour slighty:
DeepState_Run
, then it will go and look for all the test cases.DeepState_TakeOver
then we add some fakeTestInfo
structure (or maybeDeepState_TakeOver
is a macro that calls a lower level function and passes in an initializedstruct DeepState_TestInfo
), then return1
when under symbolic execution (by being hooked) and0
by default in a native execution.The text was updated successfully, but these errors were encountered: