Information included in Enpass crash reports
Whenever the Enpass app stops unexpectedly, a crash-report file is generated. This report is a set of debug logs that contains product-specific logs and configuration files of the host machine. Enpass gathers information through a crash reports using a specific script within the app’s base code. This information is useful for determining patterns in any problems that occur with the Enpass app.
The crash report does not contain sensitive or personal information. It contains only the following information:
-
Package Name
-
App Version
-
Operating system and version
-
System Language
-
Device manufacturer
-
Device model
-
Date
-
Debug data
Sample crash report
Package: in.sinew.enpass.win
Version: 114
OS: Windows 10 (10.0)
OS Version: 10
System Language: en_IN
Manufacturer: Gigabyte Technology Co., Ltd.
Model: Not set
Date: 05 September 2018 11:19:18
Operating system: Windows NT
10.0.17746
CPU: x86
GenuineIntel family 6 model 60 stepping 3
4 CPUs
GPU: UNKNOWN
Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0xffffffff8b10439b
Process uptime: not available
Thread 0 (crashed)
0 Enpass.exe + 0x9c38b
eip = 0x009bc38b esp = 0x006fc8b8 ebp = 0x006fc8dc ebx = 0x006fc9ac
esi = 0x00000009 edi = 0x68437485 eax = 0x8b10438b ecx = 0x68437485
edx = 0x00000000 efl = 0x00010202
Found by: given as instruction pointer in context
Enabling logs in Enpass to help with troubleshooting
Logs can help app developers understand what an app is doing in the background when problem occurs. If you're reporting an unusual problem to Enpass Support, we may ask you to enable logging (Settings > Advanced > Logs) and send the logs to help troubleshoot the issue.
If you have questions or need assistance:
-
Visit the Enpass Discussion Forum or contact Enpass Support