[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-tracker] [bug #25568] Duplicity seg faults
From: |
Kenneth Loafman |
Subject: |
[Duplicity-tracker] [bug #25568] Duplicity seg faults |
Date: |
Thu, 12 Feb 2009 13:03:44 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020911 Ubuntu/8.04 (hardy) Firefox/3.0.6 |
Follow-up Comment #1, bug #25568 (project duplicity):
What version of duplicity? What distro? Which Python version?
It probably has nothing to do with bug 25542. That's just a file growth
issue that I'll need to address sometime soon.
If you would, please re-run the job with:
"python -u /usr/bin/duplicity -v9 ..."
and posting the last 200 or so lines. The -u option causes stdout and stderr
to be unbuffered, so we should be able to see roughly where its at before the
segfault.
You're right, Python does not normally segfault. My guess is that its in one
of the extensions handling the IMAP protocol.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25568>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/