Hello
Usually I gdb perl and can debug (more or less) my XS code. But now I
have a situation that is making me crazy.
Module compiles an interface to a C++ library.
The interface was swig-generated.
The C library seems to work properly (as some executables that ship with
the library work).
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
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
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
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==
