View Single Post
Old 12-23-2015, 01:01 PM   #2
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,453
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
If you are using windows as your development environment then the problem is probably caused by windows not being able to buffer and write output to the screen as fast as the program can generate it. Simply redirect standard output and standard error to a file and the problem goes away. For example, when debugging calibre using print statements that generate lots of output I must use:
Code:
calibre-debug -g > foo.txt 2>&1
chaley is offline   Reply With Quote