Pressed a space bar to go to the next page while reading KJV 1900. I started the Logos with Ctrl key down. But there is no Logos4Crash file to upload. How do I create the file?
Here is Logos4Error.
8306.Logos4Error.log.
David Lee:Here is Logos4Error.
Sorry David, but that does not have anything for Beta 8. Nor can I reproduce the crash.
See http://wiki.logos.com/Diagnostic_Logging
Dave===
Windows 10 & Android 8
I am still getting the same crash quite often. Please let me know how I can create log files that will help to debug the problem.
David Lee:Please let me know how I can create log files that will help to debug the problem.
David
The link in my previous post will show you how to do that. Repeat the crash in beta 9 and upload logos4.log and any crash/error logs.
I followed as best as I could what was in the link under 4.5 Beta 9. It crashes but it does not create logos4crash log. Can you take control of my computer remotely and to see what I'm doing wrong not being able to create the crash log?
So you tried to install Beta 9?
Try starting L4 with CTRL key held down. If it crashes go to \Documents\Logos Log Files\ and upload any recent files e.g. logos4error.log, logos4.log.
Here is a error log under Beta 9.
4744.Logos4Error.log
I tried to create Logos4crash.log by starting up with CTRL key down and turning on error logging permanently as explained in the link. I could not get one. I sent logs from Logos4 and Logos4error earlier and you could not help.
David Lee: I sent logs from Logos4 and Logos4error earlier and you could not help.
Still need to see logos4.log. This should be available if you can get into Logos 4 to reproduce the error when reading KJV1900.
Here are the logs after a crash.
1452.Logos4.log
3527.Logos4Indexer.log
0486.Logos4Error.log
4048.logos4setup.log
6278.Logos4Crash.txt
It appears that a Logos4Crash log wasn't created as a result of this crash (this happens occasionally). I will send your Logos4.log file to our Development department and enter a case.
Does this happen just with the KJV 1900 or with other books as well?
David, can you please follow the instructions on http://wiki.logos.com/ProcDump to collect a native crash dump? This will help us narrow down the issue.
Procdump did not work.
David,
Does the C:\DAVID\PROCDUMP\Logos4_111215_122629.dmp exist on your system?
Yes, I zipped the file and ready to e-mail. What will be the e-mail address?
The dump was created even before Logos4 was fully initialized. The dump is not from the problem that I am reporting.
David Lee: What will be the e-mail address?
What will be the e-mail address?
Please send it to logos4feedback@logos.com
I e-mailed those files.
Here are the logs from the last crash.
2161.Logos4Indexer.log
1581.Logos4.log
5381.Logos4Error.log
I had CTRL-key pressed while LOGOS 4 started. But I do not see the crash log anywhere.
Thank you,
I have forwarded your logs (along with the dump log you mailed) to our Development department.