Valgrind gets stuck in infinite loop

Question

While testing a C programming project I encountered this error:

realloc(): invalid pointer

I tried to find the cause of the problem using Valgrind. When when I ran the code in Valgrind, it got stuck in an infinite loop in a different part of my code, and it didn't detect the invalid pointer, so I didn't get the answers I was looking for.

I guess what I want to know is: has anyone else encountered this problem with Valgrind and what's going wrong? Why does Valgrind jump into this infinite loop but when I run the code myself I just get the error.

GDB did detect the error but the info it gave me wasn't enough to fix the error; that's why I want to fix this problem I'm having with Valgrind.

Indeed show the code. Relevant outputs from the GDB wouldn't hurt either. — quinz, Jun 21 '19 at 11:50
Something you can try is to use gdb+vgdb to debug your application when it is 'looping' under valgrind. See http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver for more information. — phd, Jun 21 '19 at 20:42

score 0 · Answer 1 · answered Jun 22 '19 at 13:13

Why does Valgrind jump into this infinite loop but when I run the code myself I just get the error.

Are you sure that it was an infinite loop? Valgrind is rather slow tool. The slowdown is about 20–30 times compared to running without Valgrind. You should probably wait for 20–30 times more to get the error under Valgrind.

Valgrind gets stuck in infinite loop

1 Answers1