Re: [petsc-users] Debugging with valgrind

2022-02-09 Thread Medane TCHAKOROM
Re: Thanks for your prompts reply On 08/02/2022 19:47, Barry Smith wrote: Yes, these come from other packages or the OS so you cannot do anything about them. Barry On Feb 8, 2022, at 1:08 PM, Medane TCHAKOROM wrote: Hello , I have been debugging my code with valgrind, and found

Re: [petsc-users] Debugging with valgrind

2022-02-08 Thread Barry Smith
Yes, these come from other packages or the OS so you cannot do anything about them. Barry > On Feb 8, 2022, at 1:08 PM, Medane TCHAKOROM > wrote: > > Hello , > > I have been debugging my code with valgrind, and found many memory leakage > that i removed so far. > > But i keep

[petsc-users] Debugging with valgrind

2022-02-08 Thread Medane TCHAKOROM
Hello , I have been debugging my code with valgrind, and found many memory leakage that i removed so far. But i keep having the type of lines in my logs ==26817== 384 bytes in 1 blocks are still reachable in loss record 1,107 of 1,151 ==26817==    at 0x483877F: