-
-
Notifications
You must be signed in to change notification settings - Fork 900
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
Found 3 Fatal Exception Crashes from Testing #473
Labels
Comments
Hi! Thank you for reporting this. Once I will find some free time I will have a closer look. Good luck with your student project. Looking forward to new open source Android app analysis tool ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I'm a student researcher currently working on a project in the area of Android app analysis. As a part of the work centered around Intents, I found 3 bugs that resulted in crashes after analyzing logs/execution traces. Below are the relevant activities, traces, and adb commands that triggered the crashes.
These bugs may be hidden in unexposed Activities, but they are worth investigating into to prevent potential issues down the line and addressing to improve the overall robustness and quality. If anyone can be confirm these to be valid bugs first, I would appreciate it, and I can help provide more information as needed.
1. de.syss.MifareClassicTool.Activities.ValueBlocksToInt
Execution trace:
adb command that triggers it:
2. de.syss.MifareClassicTool.Activities.AccessConditionDecoder
Execution trace:
adb command that triggers it:
3. de.syss.MifareClassicTool.Activities.DiffTool
Execution trace:
adb command that triggers it:
The text was updated successfully, but these errors were encountered: