[lxml-dev] Segfault in lxml 1.3.2

[Stefan Behnel]

Hi,

Itamar Shtull-Trauring wrote:
> One of my co-workers is getting an occasional segfault in some code using
> lxml; it uses no other non-stdlib libraries, and it's single threaded. The
> segfault is in:
> 
> __pyx_tp_dealloc_5etree__Element (src/lxml/etree.c:11282).

That's definitely a weird place for a crash. I definitely need more infos here.


> Any info I can try to get to help debug this? Would a core dump be
> helpful? He's so far been unable to create a minimal reproducing example.

What usually helps more than a core dump is a crash under valgrind control.
The Makefile has a command line for it. Valgrind usually prints the exact
error, the original reason why that memory location is not accessible (where
it was freed or allocated) and what was the last thing that happened when it
crashed.

Stefan