Hi ael, thanks for this! Unfortunately, as you suspect, the backtrace is not useful without debugging information. :-/
I've just uploaded a version of jigdo-file which contains debugging symbols: <http://atterer.net/jigdo-file_0.7.3-2_i386.deb> Maybe retry with it and see if you can trigger the problem again. Please also add "--debug=all" to jigdoOpts in your ~/.jigdo-lite configuration file to get more information! What exactly is happening during the livelock? Does jigdo-file take up all CPU time, or does it just appear to hang? How long have you waited before interrupting it? The code has not changed significantly in a long time and AFAIR, you're the first to report this kind of problem. This makes me think that something must be special about your setup - anything unusual that you can think of? Are you running several jigdo downloads in parallel with the same cache file? Please also send me the contents of your ~/.jigdo-lite file. > This livelock was *not* cleared by removing temporary files. Did you also remove the cache? What else was the machine doing at the time, was any other software apart from the regular desktop stuff running? What filesystem are you creating your images on? Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ '` ¯ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
