Comment 7 for bug 1641099
Revision history for this message
| Ryan C. Underwood (nemesis-icequake) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
I also had this segfault, and deleting the named socket also fixed it.
The only difference I could observe is that the initial connect() call to the socket produced -1 ECONNREFUSED on a failed run (where it already existed), and on a successful run (where it did not already exist) the connect() call produced -1 ENOENT. Everything subsequent looked identical until the crash. Could it just be bogus error handling when a defunct named socket is left around due to a system crash, resume failure, etc?