Re: [libvirt] Track an error
On Sat, Jun 28, 2014 at 08:52:32AM +0300, David kiarie wrote:
Hi there,
Just a silly question, do we have a simpler way of checking where
exactly a test is failing.The tests are failing after hacking stuff
around.
I have this error
../build-aux/test-driver: line 95: 20128 Segmentation fault "$@"
> $log_file 2>&1
Yes am having a segfault!
I don't know how to track it, well, I could review the whole file but
is there some other method I am missing.Could you help me interpret
the error, what does 20128 stand for?
I believe that's the pid, best way is changing into the tests
directory and running "../run gdb <test>", where <test> is the test
that's segfaulting.
Martin
Attachments:
- signature.asc (application/pgp-signature — 819 bytes)