From my understanding, the process_monitor stores crashbin information locally. If this is running on a virtual machine and a test case causes the process and target machine to become unresponsive, vmcontrol would then revert to an earlier snapshot. How is the crashbin information displayed to the web interface, or accessed at this point if it was lost on the revert to an earlier snapshot?
Asked
Active
Viewed 116 times
1
-
I'm voting to close this question as off-topic because it appears to be beyond the scope of SO – Strawberry Nov 22 '15 at 19:19
-
Okay, thanks anyways! – Stephen McKeon Nov 22 '15 at 23:39
-
@Strawberry Why does it seem off-topic? This seems to me to fall under the category of "software tools commonly used by programmers." http://stackoverflow.com/help/on-topic – jtpereyda Nov 25 '15 at 00:03
-
@JoshP I would suggest that a combined total of 88 questions and 20 followers rather proves my point - but mine is just one solitary vote – Strawberry Nov 25 '15 at 00:27
-
@Strawberry Do you mean to say that this tool is not common enough to qualify? – jtpereyda Dec 04 '15 at 18:58
1 Answers
1
After walking through most of the code in the Sulley environment, I found that the restart_target() method in the sessions.py module calls for a restart on the virtual machine if vmcontrol is available first, and then tries to restart the process via the procmon if its available. By switching the order of these, I can solve the problem of losing the log information from the crashbin unless the entire target machine becomes unresponsive.
Stephen McKeon
- 31
- 4
-
Nice! Please consider making a pull request to the Github site, and also to my fork https://github.com/jtpereyda/sulley – jtpereyda Nov 23 '15 at 06:47