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
I downloaded and largely can run symbiotic from the zenodo link referenced in your paper on symbiotic 10.
Unfortunately, enabling prp=memsafety results in symbiotic erroring out with an "unable to instrument code" error.
In the symbiotic 10 paper the authors noted predator did not / was not integrated with that version of symbiotic, and so I am perplexed as to why symbiotic is invoking it.
Is there a way to disable predator?
Or does the most recent (sv25 branch) properly deal with predator integration?
The text was updated successfully, but these errors were encountered:
In case anyone is wondering -- When invoked without "--memsafety-config-file", symbiotic defaults to the config file "config_marker.json."
This config file specifies a number of shared objects which are invoked as analysis passes in LLVM. One of the shared objects listed has "predator" in its name.
In order to get a working run, I used config_markerk.json, but removed all of the analyses (shared objects) except "libdgPointsToPlugin.so".
I downloaded and largely can run symbiotic from the zenodo link referenced in your paper on symbiotic 10.
Unfortunately, enabling prp=memsafety results in symbiotic erroring out with an "unable to instrument code" error.
In the symbiotic 10 paper the authors noted predator did not / was not integrated with that version of symbiotic, and so I am perplexed as to why symbiotic is invoking it.
Is there a way to disable predator?
Or does the most recent (sv25 branch) properly deal with predator integration?
The text was updated successfully, but these errors were encountered: