-
|
When running emba against different software, some times a module runs for a very long time (or even hang - not 100% sure). Is there a way to stop the long running modules in middle by setting maximum running time and let the overall process to complete ? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
The danger of such a quick implementation is to leave the modules in a inconsistent state which will cause massive issues. As such a feature needs quite huge refactoring on every module it is currently not possible to limit the modules by time. If a module is really hanging we need to dig into this case to fix it. Please open an issue with a reproducable test case. So, we can do a root cause analysis on this problem. |
Beta Was this translation helpful? Give feedback.
-
When running emba against a same software package with java, .so and .dll files multiple times, one out of about 10 runs will hang on multiple modules, S24_kernel_bin_identifier, S06_distribution_identification, S22_php_check, S95_interesting_files_check, S107_deep_password_search. The most observed hanging module is S107_deep_password_search. In all successful runs, it took at most 30 minutes to finish. In the hang runs, all took more than up to 10 hours and not finished at all. The challenge for me to identify the exact causes is that it is not always reproduceable, only 1 out of ~10 runs and totally random. No helpful information can be found in all log files. Any suggestions how shall I better tracking the issues ? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Very interesting case. Please open a dedicated issue with the affected Firmware/binary. So that I can try to reproduce it. |
Beta Was this translation helpful? Give feedback.
-
Thanks for offering help. Unfortunately, the codes belongs to our vendors and thus not suitable to share here. |
Beta Was this translation helpful? Give feedback.
-
|
Happy debugging |
Beta Was this translation helpful? Give feedback.
The danger of such a quick implementation is to leave the modules in a inconsistent state which will cause massive issues. As such a feature needs quite huge refactoring on every module it is currently not possible to limit the modules by time. If a module is really hanging we need to dig into this case to fix it. Please open an issue with a reproducable test case. So, we can do a root cause analysis on this problem.