Open p1v07 opened 10 months ago
Describe the bug android hooking dumped information printed in the concurrent scenario is confusing.
To Reproduce Steps to reproduce the behavior:
android hooking watch class_method okhttp3.internal.connection.RealCall.execute --dump-args --dump-backtrace --dump-return
Similar issues
Expected behavior args backtrace and return should be consistent.
Evidence / Logs / Screenshots
The second backtrace should be associated with the first Return value
Environment (please complete the following information):
Application
any android app using okhttp
Additional context Add any other context about the problem here.
Describe the bug android hooking dumped information printed in the concurrent scenario is confusing.
To Reproduce Steps to reproduce the behavior:
android hooking watch class_method okhttp3.internal.connection.RealCall.execute --dump-args --dump-backtrace --dump-returnSimilar issues
Expected behavior args backtrace and return should be consistent.
Evidence / Logs / Screenshots
The second backtrace should be associated with the first Return value
Environment (please complete the following information):
Application
any android app using okhttp
Additional context Add any other context about the problem here.