02-01-2011, 03:37 PM | #1 |
Sigil developer
Posts: 1,274
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
|
Calibre debug file
For some reason I can't seem to find the debug file created when running the comand line:
Code:
calibre-debug --gui-debug=GUI_DEBUG It works fine if I use the GUI menu option to restart in debug mode - the /tmp file gets created and gets displayed after logging out and can be edited. I must be missing something obvious. Any pointers? |
02-01-2011, 03:56 PM | #2 |
Wizard
Posts: 3,130
Karma: 91256
Join Date: Feb 2008
Location: Germany
Device: Cybook Gen3
|
My guess would be that the file gets created either in the current working directory of the shell you called the program from or in Calibre's bin directory.
Edit: I just tested. The debug file doesn't get displayed for me, as well. Edit2: I guessed wrong. A search didn't find the file. There's another way to create a logfile that should work: Invoke "calibre-debug -g > filename", that should redirect the output to the filename you selected. This will be created in the current working directory, unless you specify an absolute path. Last edited by Manichean; 02-01-2011 at 04:04 PM. |
Advert | |
|
02-01-2011, 04:10 PM | #3 |
Sigil developer
Posts: 1,274
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
|
Yeah, I've been using "calibre-debug --gui-debug=GUI_DEBUG | tee out " to capture it - good to know there's a '-g' to use - I just added the tee in the script and left it since it worked, but was curious if I was just misreading the options.
|
02-01-2011, 04:18 PM | #4 |
Wizard
Posts: 3,130
Karma: 91256
Join Date: Feb 2008
Location: Germany
Device: Cybook Gen3
|
I don't think you're misreading anything, you may have found a bug. Either that, or we both misread something.
|
02-01-2011, 04:31 PM | #5 |
creator of calibre
Posts: 44,384
Karma: 23766374
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
There is no debug file created by calibre-debug -g
debug output is printed to stdout snd stderr use calibre-debug -g 2>&1 > log.txt Or relaunch calibre in debug mode by clicking the arrow next to preferences, in which case a debug file will be created and automatically displayed after you quit calibre. |
Advert | |
|
02-01-2011, 04:36 PM | #6 |
Wizard
Posts: 3,130
Karma: 91256
Join Date: Feb 2008
Location: Germany
Device: Cybook Gen3
|
|
02-01-2011, 04:44 PM | #7 |
creator of calibre
Posts: 44,384
Karma: 23766374
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
Ah no, that option and --show-gui-debug are both for internal use. I'll add a note to the help for those options.
|
02-01-2011, 04:45 PM | #8 |
Wizard
Posts: 3,130
Karma: 91256
Join Date: Feb 2008
Location: Germany
Device: Cybook Gen3
|
Oh, okay. In that case, to conclude @OP: Go with the calibre-debug -g > outputfile option.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
"debug" in Calibre | wrenn1 | Kobo Reader | 3 | 08-24-2010 02:41 PM |
Calibre: wie aktiviert man das Debug Verzeichnis? | nalor78 | Software | 1 | 08-10-2010 09:38 AM |
What happened to calibre-debug "--develop-from" option? | macr0t0r | Calibre | 6 | 12-03-2009 07:22 PM |
calibre-debug --update-module | iain_benson | Calibre | 4 | 10-02-2009 07:00 PM |
Debug mode of HanLin v3 | sang | HanLin eBook | 4 | 07-01-2009 04:00 PM |