Geek asks and answers

Valgrind "Killed" Message

I am running a program that does not work with an interrupt interrupt (error code 12). To debug the error, I run valgrind, but every time I run it, valgrind itself crashes with the message "Killed", and nothing else (the total amount of the message heap, etc. Does not appear). I can't find anything on google or SO about this, and I hope someone can shed some light on what causes this error and how to debug it.

Any help is appreciated!

+5
source share
2 answers

I think your process is likely to be killed by the Out Of Memory kernel system - when the system runs out of memory, which will be hard to kill the process in a way that cannot be captured, so Valgrind quits without saying anything.

Presumably, your program uses a lot of memory, and when run under valgrind, where additional memory is required to track the certainty of the memory, there is not enough memory, and the process (probably very large) valgrind gets killed.

If I'm right, you will need a machine with more memory, or at least a larger replacement, to be able to run your program under valgrind.

+5
source

, , , (GPU, FPGA), , .

valgrind.

0

More articles:


All Articles