[lxml-dev] Tracking down bugs

[Filip Salomonsson]

On Thu, Dec 4, 2008 at 15:37, Stefan Behnel <stefan_ml at behnel.de> wrote:
>
> First of all, use the latest released (!) version of lxml and build it
> without having Cython installed and with debug symbols enabled (add "-g3"
> to your CFLAGS)

> Then, install valgrind and try to make your program crash under valgrind
> control.

Excellent; thanks! I'll try that and see what I can find. (Hadn't
noticed 2.1.3, really - I'll go get that regardless.)

> Stripping down your program to a shorter snippet that shows the crash more
> or less reliably is a very good way to track down the circumstances that
> are required to trigger the problem.

Sure will - if and when I'm able to provoke a repeatable crash. It all
seems annoyingly random so far.

> Lastly, if you know how to use gdb and can investigate a bit more, any
> further hints that you find can be helpful in tracking down the problem.

I'm afraid gdb is mostly black voodoo magic to me so far, but I'll
probably try to dive into it if I get to the point where that seems
useful.

Thank you,

Filip
(If I didn't have lxml, I think my job would be really tedious, so
thanks for that too!)