Re: Debugging a XS problem.. where to start?

2012-01-16 Thread Marvin Humphrey
On Mon, Jan 16, 2012 at 07:05:13PM +, Alberto Simões wrote: GDB doesn't show much info as well: Any idea where should I look? I'd advocate trying a run under Valgrind, which can sometimes reveal the cause for a problem when GDB only reveals the effect. Marvin Humphrey

Re: Debugging a XS problem.. where to start?

2012-01-16 Thread Alberto Simões
On 16/01/12 19:52, Marvin Humphrey wrote: On Mon, Jan 16, 2012 at 07:05:13PM +, Alberto Simões wrote: GDB doesn't show much info as well: Any idea where should I look? I'd advocate trying a run under Valgrind, which can sometimes reveal the cause for a problem when GDB only reveals

Re: Debugging a XS problem.. where to start?

2012-01-16 Thread Marvin Humphrey
On Mon, Jan 16, 2012 at 09:11:27PM +, Alberto Simões wrote: I do not use valgrind for some time, but this seems awkward: [ambs@stravinski FreeLing-old]$ valgrind -- /usr/bin/perl -I blib/arch/ -I blib/lib/ t/01-bindings/01-tokenizer.t ==13831== Memcheck, a memory error detector

Re: Debugging a XS problem.. where to start?

2012-01-16 Thread Alberto Simões
On 16/01/12 21:28, Marvin Humphrey wrote: On Mon, Jan 16, 2012 at 09:11:27PM +, Alberto Simões wrote: I do not use valgrind for some time, but this seems awkward: [ambs@stravinski FreeLing-old]$ valgrind -- /usr/bin/perl -I blib/arch/ -I blib/lib/ t/01-bindings/01-tokenizer.t ==13831==