Skip to content
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

script has been destroyed #7

Open
maru7777 opened this issue May 13, 2024 · 1 comment
Open

script has been destroyed #7

maru7777 opened this issue May 13, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@maru7777
Copy link

after logging for 2min, the script is stucked ,and after pressing ctrl+c ,it shows:
2024-05-13 22:49:20,660 CRITICAL | Aw, Snap! Something went wrong: script has been destroyed.
the OS is IOS 15.4,frida 16.2.1

@myr-syn
Copy link
Collaborator

myr-syn commented Jun 3, 2024

Hi,

This error: Aw, Snap! Something went wrong: script has been destroyed is a normal message that occurs when the Python script is interrupted by ctrl+c.

It seems that you are trying to trace a function that performs too many instructions before returning, which could explain that the tracer runs for at least 2 minutes. However, you should be able to load the partially-generated trace after interrupting the script.

@myr-syn myr-syn added the help wanted Extra attention is needed label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants