|
From: subhasish K. <sub...@gm...> - 2019-06-24 16:33:20
Attachments:
valgrind.log
valgrind-track-origin.log
|
Hi, I am using embedded linux to run my application. I do not get any memory leak information with valgrind, when I set “ *--track-origins=yes*”. Without *--track-origins* option, I can see memory leak errors, but file name and line number is not displayed. I have attached valgrind logs for reference. My application is compiled with “*-g -o0*” compiler flags and my open-embedded core does not support GDB. Kindly let me know, how to get more debug information for memory leaks in my application. Thanks for your support, Subhasish |
|
From: Julian S. <js...@ac...> - 2019-06-24 19:10:49
|
I guess that the problem is that the build of valgrind somehow removed the debug (unwind) information on /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so and that's why there is no backtrace. Can you rebuild valgrind so that the debug information on that file is preserved? J |
|
From: subhasish K. <sub...@gm...> - 2019-06-25 09:58:09
|
Hi, Can someone help me to resolve this issue. Thanks, Subhasish On Mon, Jun 24, 2019 at 10:03 PM subhasish Karmakar < sub...@gm...> wrote: > Hi, > > I am using embedded linux to run my application. > > I do not get any memory leak information with valgrind, when I set “ > *--track-origins=yes*”. > > Without *--track-origins* option, I can see memory leak errors, but file > name and line number is not displayed. > > I have attached valgrind logs for reference. > > > > My application is compiled with “*-g -o0*” compiler flags and my > open-embedded core does not support GDB. > Kindly let me know, how to get more debug information for memory leaks in > my application. > > Thanks for your support, > Subhasish > |
|
From: John R. <jr...@bi...> - 2019-06-25 13:33:56
|
On 6/25/19 09:57 UTC, subhasish Karmakar wrote:
> Hi,> Can someone help me to resolve this issue.
Did you read Julian Seward's response of Mon, 24 Jun 2019 21:10:48 +0200 ?
What does the shell command
file /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so
report? If the output contains the word "stripped", then
that likely is the problem. Rebuild so that it is not stripped.
|
|
From: subhasish K. <sub...@gm...> - 2019-06-26 06:27:54
Attachments:
valgrind_3.14.0.bb
|
Hi Julian, Below file is still stripped even after rebuilding, /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so I am using attched bitbake receipe to build valgrind. Can I modify the recipe file so that debug infromation is always included in vgpreload_memcheck-arm-linux.so ? Thanks, Subhasish On Tue, Jun 25, 2019 at 12:40 AM Julian Seward <js...@ac...> wrote: > > I guess that the problem is that the build of valgrind somehow removed > the debug (unwind) information on > /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so > and that's why there is no backtrace. Can you rebuild valgrind so that > the debug information on that file is preserved? > > J > |
|
From: subhasish K. <sub...@gm...> - 2019-07-02 10:28:45
|
Hi Julian, "/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so" file is still stripped even after rebuilding. Could you please suggest some way to resolve this issue. Thanks, Subhasish On Wed, Jun 26, 2019 at 11:57 AM subhasish Karmakar < sub...@gm...> wrote: > Hi Julian, > > Below file is still stripped even after rebuilding, > /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so > > I am using attched bitbake receipe to build valgrind. > Can I modify the recipe file so that debug infromation is always included > in vgpreload_memcheck-arm-linux.so ? > > Thanks, > Subhasish > > On Tue, Jun 25, 2019 at 12:40 AM Julian Seward <js...@ac...> wrote: > >> >> I guess that the problem is that the build of valgrind somehow removed >> the debug (unwind) information on >> /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so >> and that's why there is no backtrace. Can you rebuild valgrind so that >> the debug information on that file is preserved? >> >> J >> > |
|
From: Mark W. <ma...@kl...> - 2019-07-02 11:14:54
|
On Tue, 2019-07-02 at 15:58 +0530, subhasish Karmakar wrote: > Hi Julian, > "/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so" file is still > stripped > even after rebuilding. > Could you please suggest some way to resolve this issue. A normal build doesn't remove debug information. How did you build exactly? If you follow the build instructions in the README you should get a normal, not stripped vgpreload library. Cheers, Mark |