Re: [Valgrind-users] MySQL related messages

2020-06-07 Thread Paul FLOYD
On 6/7/20 16:11 UTC, James Read wrote: > I found the FAQ https://dev.mysql.com/doc/refman/8.0/en/faqs.html but > couldn't find the answer you were referring to. > Any clues as to which part of the FAQ I should be looking in? I think that John was referring to the Valgrind FAQ https://www.valgri

Re: [Valgrind-users] MySQL related messages

2020-06-07 Thread John Reiser
After a few private emails and --num-callers=50, then the original poster reports: mysql_library_end() was missing. Error messages have gone now. ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/li

Re: [Valgrind-users] MySQL related messages

2020-06-07 Thread James Read
On Sun, Jun 7, 2020 at 7:04 PM John Reiser wrote: > On 6/7/20 16:11 UTC, James Read wrote: > > Any idea what this means?: > > > > ==56082== 16,528 bytes in 1 blocks are possibly lost in loss record 409 > of 409 > > Help yourself; that question is bad lazy. There is a manual with > extensive docu

Re: [Valgrind-users] MySQL related messages

2020-06-07 Thread John Reiser
On 6/7/20 16:11 UTC, James Read wrote: Any idea what this means?: ==56082== 16,528 bytes in 1 blocks are possibly lost in loss record 409 of 409 Help yourself; that question is bad lazy. There is a manual with extensive documentation. A brief search of the web will reveal the answer. The ma

Re: [Valgrind-users] MySQL related messages

2020-06-07 Thread James Read
Any idea what this means?: ==56082== 16,528 bytes in 1 blocks are possibly lost in loss record 409 of 409 ==56082==at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==56082==by 0x49D76F7: my_raw_malloc (my_malloc.cc:199) ==56082==by 0x49D76F

Re: [Valgrind-users] MySQL related messages

2020-06-05 Thread Alexander Brock
On 6/5/20 3:28 PM, James Read wrote: > I'm guessing I'm going to have to compile MySQL with -g flag in order to > decipher this stuff? Some distributions have extra packages with debug symbols, if you install them you should get decent messages. Best Regards, Alexander _

Re: [Valgrind-users] MySQL related messages

2020-06-05 Thread Paul FLOYD
Hi If you want to be certain then you will need to run with debug information. There may be something like a "mysql-debuginfo" package that you could install. That said, "still reachable" memory is often harmless, caused by libraries caching information. Similar questions have been asked on Sta

[Valgrind-users] MySQL related messages

2020-06-05 Thread James Read
I have a bunch of what seem to be MySQL related messages for my crawler at https://github.com/JamesRead5737/webcrawler ==371932== 3,416 bytes in 61 blocks are still reachable in loss record 406 of 408 ==371932==at 0x483BE63: operator new(unsigned long) (in /usr/lib/x86_64-linux-gnu/valgrind/vg