<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Valgrind doesn't work even after installing glibc-debuginfo. in Photon OS Discussions</title>
    <link>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2988534#M395</link>
    <description>&lt;P&gt;Thanks for sharing&lt;/P&gt;</description>
    <pubDate>Wed, 27 Sep 2023 09:49:15 GMT</pubDate>
    <dc:creator>miladmeh8</dc:creator>
    <dc:date>2023-09-27T09:49:15Z</dc:date>
    <item>
      <title>Valgrind doesn't work even after installing glibc-debuginfo.</title>
      <link>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2980327#M391</link>
      <description>&lt;P&gt;I'm trying to test vmcad with Valgrind and get following error message. I follow the instructions to install glibc-debuginfo but the message still shows up. I have no idea how to solve this problem. Any reply will be appreciated.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;root@localhost [ ~/valgrind-3.21.0 ]# valgrind --track-origins=yes /usr/lib/vmware-vmca/sbin/vmcad -L
==43762== Memcheck, a memory error detector
==43762== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==43762== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==43762== Command: /usr/lib/vmware-vmca/sbin/vmcad -L
==43762==

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strlen
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.  The package you need
valgrind:  to install for fix (1) is called
valgrind:
valgrind:    On Debian, Ubuntu:                 libc6-dbg
valgrind:    On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
valgrind:
valgrind:  Note that if you are debugging a 32 bit process on a
valgrind:  64 bit system, you will need a corresponding 32 bit debuginfo
valgrind:  package (e.g. libc6-dbg:i386).
valgrind:
valgrind:  Cannot continue -- exiting now.  Sorry.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enviroment&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;root@localhost [ ~/valgrind-3.21.0 ]# uname -a
Linux localhost 4.19.269-3.ph3 #1-photon SMP Wed Jan 11 01:14:06 UTC 2023 x86_64 GNU/Linux
root@localhost [ ~/valgrind-3.21.0 ]# lsb_release
Distributor ID: VMware Photon OS
Description:    VMware Photon OS 3.0
Release:        3.0
Codename:       Photon&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;root@localhost [ ~/valgrind-3.21.0 ]# yum install glibc-debuginfo
Package glibc-debuginfo is already installed.
Nothing to do.&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 02 Aug 2023 03:31:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2980327#M391</guid>
      <dc:creator>lewislee</dc:creator>
      <dc:date>2023-08-02T03:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Valgrind doesn't work even after installing glibc-debuginfo.</title>
      <link>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2980363#M392</link>
      <description>&lt;P&gt;my glibc version isn't up to date, so the debuginfo version doesn't match the glibc version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;run this command and the problem gets solved.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;yum update glibc&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 08:52:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2980363#M392</guid>
      <dc:creator>lewislee</dc:creator>
      <dc:date>2023-08-02T08:52:18Z</dc:date>
    </item>
    <item>
      <title>Re: Valgrind doesn't work even after installing glibc-debuginfo.</title>
      <link>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2988534#M395</link>
      <description>&lt;P&gt;Thanks for sharing&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2023 09:49:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Photon-OS-Discussions/Valgrind-doesn-t-work-even-after-installing-glibc-debuginfo/m-p/2988534#M395</guid>
      <dc:creator>miladmeh8</dc:creator>
      <dc:date>2023-09-27T09:49:15Z</dc:date>
    </item>
  </channel>
</rss>

