Ctrl-Shft-R Debug vs calibre-debug -g

JimmXinu · 11-19-2014, 11:56 PM

I've noticed a couple of odd things about the two debug modes. I'm using caliber 2.10 on Win8.

First:

If I'm already in Ctrl-Shft-R debug mode and hit Ctrl-R to restart, calibre restarts and says it's in debug mode with the same debug file, but it doesn't write anything more to the debug text file.

It looks like there should be another check at calibre/gui2/main.py:347. I don't know what's most appropriate. Perhaps: u'--gui-debug' in sys.argv ?

Second:

Trying to debug a FileTypePlugin, print statements from run() etc don't show up in the console output when I'm using calibre-debug -g. They do appear in the text file when using Ctrl-Shft-R debug.

I don't have any ideas about that one.

kovidgoyal · 11-20-2014, 06:01 AM

https://github.com/kovidgoyal/calibr...51632300cb39b2

As for the second, I think that's a peculiarity of the windows console, calibre-debug -g should work if you redirect its output to a file, like this

calibre-debug -g > log.txt 2>&1

kovidgoyal · 11-20-2014, 07:33 AM

And here's a fix for the second issue, windows is such a pain

https://github.com/kovidgoyal/calibr...b9b5991f0c0721

JimmXinu · 11-20-2014, 10:57 AM

Both work for me. Thanks!

11-19-2014, 11:56 PM	#1
JimmXinu Plugin Developer Posts: 7,155 Karma: 5006097 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	Ctrl-Shft-R Debug vs calibre-debug -g I've noticed a couple of odd things about the two debug modes. I'm using caliber 2.10 on Win8. First: If I'm already in Ctrl-Shft-R debug mode and hit Ctrl-R to restart, calibre restarts and says it's in debug mode with the same debug file, but it doesn't write anything more to the debug text file. It looks like there should be another check at calibre/gui2/main.py:347. I don't know what's most appropriate. Perhaps: u'--gui-debug' in sys.argv ? Second: Trying to debug a FileTypePlugin, print statements from run() etc don't show up in the console output when I'm using calibre-debug -g. They do appear in the text file when using Ctrl-Shft-R debug. I don't have any ideas about that one.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Does anyone know how to read a Calibre debug log file?	TomOnMobread	Calibre	7	12-11-2012 02:57 PM
Calibre + Kobo Touch debug info	Blue2u	Devices	7	04-09-2012 11:27 PM
Calibre - Kobo Vox debug	jeather	Devices	4	11-01-2011 08:43 PM
Calibre debug file	meme	Calibre	7	02-01-2011 05:45 PM
calibre-debug --update-module	iain_benson	Calibre	4	10-02-2009 08:00 PM

11-20-2014, 06:01 AM	#2
kovidgoyal creator of calibre Posts: 45,634 Karma: 28549046 Join Date: Oct 2006 Location: Mumbai, India Device: Various	https://github.com/kovidgoyal/calibr...51632300cb39b2 As for the second, I think that's a peculiarity of the windows console, calibre-debug -g should work if you redirect its output to a file, like this calibre-debug -g > log.txt 2>&1

11-20-2014, 07:33 AM	#3
kovidgoyal creator of calibre Posts: 45,634 Karma: 28549046 Join Date: Oct 2006 Location: Mumbai, India Device: Various	And here's a fix for the second issue, windows is such a pain https://github.com/kovidgoyal/calibr...b9b5991f0c0721

11-20-2014, 10:57 AM	#4
JimmXinu Plugin Developer Posts: 7,155 Karma: 5006097 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	Both work for me. Thanks!

Advert