View Single Post
Old 05-13-2017, 11:04 PM   #3
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by kovidgoyal View Post
On windows there is no good way -- the minimum you would need to do is rebuild calibre from source yourself with debugging symbold turned on and either use windebug or the visual studio debugger or failing those two stick lots of printf() statements into the relevant code path.
Figures...

Quote:
Generally with MTP crashes it is typically the windows portable device susbsystem returning unexpected data to calibre. Simply rebooting the device and the computer might fix it.
As mentioned, I tried that, and the crash occurred again after I had rebooted both devices.

What next? Remove the Calibre metadata file from the mobile device and let Calibre attempt to rebuild it from scratch?
______
Dennis
DMcCunney is offline   Reply With Quote