-
-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analysis stuck in S26 #1485
Comments
Could yo provide a firmware for testing |
Unfortunately not, we run emba on different firmware that is currently in development and I am not allowed to publish that. I also checked an older firmware, it shows the same error, I also checked that I already ran a successful emba scan on that firmware end of January (probably an emba version from late December / early January in that case). I will try to do a bit of testing if the testcase runs from an older emba version, but do you have an idea what might go wrong? Can also provide more logging if necessary. |
I went back to the version of the 15th of January and the module runs as expected. I will see that I either track down the problem or provide a stripped down firmware version. But will be probably next week until I can provide more information. |
As soon as we have something for reproducing this issue I will take a look at it |
This looks quite ok for me |
Describe the bug
Trying to run emba on a new custom firmware (still have to confirm if the problem also exists on older firmware). The analysis was stuck for 5 hours in S26 trying to compile the kernel. This was the last log entry from S26:
[*] Starting kernel compile dry run ...
The kernel-compile.log has almost 500 MB. It seems it was stuck in a loop, the same log entries repeat after about 1.200 lines over and over again. Will try to attach the log.
OS. Kali 2024.04
Priority issue
Are you already a [Sponsor]? - [N]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: