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

On 16/01/12 19:52, Marvin Humphrey wrote:
> On Mon, Jan 16, 2012 at 07:05:13PM +0000, 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.
>

Hello.

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
==13831== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==13831== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==13831== Command: /usr/bin/perl -I blib/arch/ -I blib/lib/ 
t/01-bindings/01-tokenizer.t
==13831==


and... nothing... I need to kill it.
Ideas?