Comment 5 for bug 2017853
Revision history for this message
| Sergio Durigan Junior (sergiodj) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Thanks for the followup.
I read lxml's code and commits from 4.8.0 (the version we have in Jammy) to 4.9.1 (the version you confirmed to be working). There is really nothing that stands out. There are some minor things that caught my attention, but I'm not convinced that any of them is related to this issue.
The best scenario here would be to have a reproducer for this bug. I understand that this may not be possible/feasible, so I would like to request more data from you:
- Could you provide more details about the stack trace? For example, were you able to obtain a stack trace for lxml as well, since the bug happens there?
- Can you check if the segfault happens with version 4.9.0 from pip, please? And while you're at it, can you double check that you can still reproduce the problem with version 4.8.0 *from pip*?
- I know that lxml needs C bindings to work, and it probably compiles them when you install the package using pip. I'm wondering if there's some compiler flag that's affecting the bindings. My first guess would be LTO, but I noticed that it's not enabled for the build.