As there has been no activity on this bug and it appears to be fixed,
I'm closing it.
** Changed in: pida (Ubuntu)
Status: Confirmed => Fix Released
--
pida seg faults
https://launchpad.net/bugs/41827
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
Indeed this seem fixed in 0.3.0 . I tested using the source package.
--
pida seg faults
https://launchpad.net/bugs/41827
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
This bug has been fixed upstream.
--
pida seg faults
https://launchpad.net/bugs/41827
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
I can confirm this behaviour with 0.2.2-2ubuntu2. I don't know how to
obtain a backtrace from python programs though.
** Changed in: pida (Ubuntu)
Status: Unconfirmed => Confirmed
--
pida seg faults
https://launchpad.net/bugs/41827
--
universe-bugs mailing list
universe-bugs@lists.ubuntu
** Changed in: pida (Ubuntu)
Assignee: (unassigned) => MOTU
--
pida seg faults
https://launchpad.net/bugs/41827
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs