e98bf342e7
Otherwise, stuff that inherits logger functions on require don't get logged (i.e., framebuffer), and the debug guards aren't hooked.
1.3 KiB
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Bug report | Create a bug report to help us improve the application |
- KOReader version:
- Device:
Issue
Steps to reproduce
crash.log (if applicable)
crash.log is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:
/mnt/private/koreaderfor Cervanteskoreader/directory for Kindle.adds/koreader/directory for Koboapplications/koreader/directory for Pocketbook
Android logs are kept in memory. Please go to [Menu] → Help → Bug Report to save these logs to a file.
Please try to include the relevant sections in your issue description.
You can upload the whole crash.log file (zipped if necessary) on GitHub by dragging and dropping it onto this textbox.
If your issue doesn't directly concern a Lua crash, we'll quite likely need you to reproduce the issue with verbose debug logging enabled before providing the logs to us.
To do so, from the file manager, go to [Tools] → More tools → Developer options, and tick both Enable debug logging and Enable verbose debug logging.
You'll need to restart KOReader after toggling these on.
If you instead opt to inline it, please do so behind a spoiler tag:
crash.log
<Paste crash.log content here>