Re: set up Valgrind for multiple targets
Mark Roberts <[email protected]> Fri, 16 Jan 2026 13:45:42 -0800
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
--===============7890445734130181005== Content-Type: multipart/alternative; boundary="00000000000074feb006488843b5" --00000000000074feb006488843b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am using Ubuntu 25.10 running in a WSL2 box on win 10. Didn't realize I needed to rebuild after installing 32bit runtime. All is looking much better. Except now I have to debug our tool running on 32 bits. =F0=9F=98=8A Thanks, Mark -----Original Message----- From: Paul Floyd via Valgrind-users <[email protected]> Sent: Friday, January 16, 2026 12:55 PM To: [email protected] Subject: Re: [Valgrind-users] set up Valgrind for multiple targets On 2026-01-16 21:05, Mark Roberts wrote: > I'd like to be able to use Valgrind on both x86 and x86-64 binaries > running on my x64-64 linux system. I quite familiar with building and > using Valgrind on X86-64 binaries, we use Valgrind as the framework to > build our DynComp tool to do comparability analysis and type inference > of C/C++ programs. I would like to do the same for x86 binaries, but > I am unsure of the process to setup a secondary target. > Hi Mark What OS are you using? At the moment I mainly use FreeBSD amd64, Fedora Linux amd64 and a bit of openSUSE amd64. For systems where I have the full 32bit subsystem installed then all I have to do is run configure. Autoconf should detect both amd64 and x86 and build both of them. So really all that you need to to is to install the x86 libc. You need the x86 C++ standard lib if you want to run the regression tests. openSUSE has removed the x86 startup file from gcc so it can no longer build x86 binaries (it will still run them). So in some cases you may need to build a compiler for the platform. Regards Paul _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users --00000000000074feb006488843b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset= =3Dutf-8"><meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered m= edium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-link:"Plain Text"; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style></head><body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" s= tyle=3D"word-wrap:break-word"><div class=3D"WordSection1"><p class=3D"MsoPl= ainText">I am using Ubuntu 25.10 running in a WSL2 box on win 10.</p><p cla= ss=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText">Didn't realize = I needed to rebuild after installing 32bit runtime.=C2=A0 All is looking mu= ch better. Except now I have to debug our tool running on 32 bits. <span st= yle=3D"font-family:"Segoe UI Emoji",sans-serif">=F0=9F=98=8A</spa= n></p><p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText">Thanks,= Mark</p><p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText">----= -Original Message-----<br>From: Paul Floyd via Valgrind-users <<a href= =3D"mailto:[email protected]">[email protected]= eforge.net</a>> <br>Sent: Friday, January 16, 2026 12:55 PM<br>To: <a hr= ef=3D"mailto:[email protected]">[email protected]= rceforge.net</a><br>Subject: Re: [Valgrind-users] set up Valgrind for multi= ple targets</p><p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText= ">=C2=A0</p><p class=3D"MsoPlainText">On 2026-01-16 21:05, Mark Roberts wro= te:</p><p class=3D"MsoPlainText">> I'd like to be able to use Valgri= nd on both x86 and x86-64 binaries </p><p class=3D"MsoPlainText">> runni= ng on my x64-64 linux system.=C2=A0 I quite familiar with building and </p>= <p class=3D"MsoPlainText">> using Valgrind on X86-64 binaries, we use Va= lgrind as the framework to </p><p class=3D"MsoPlainText">> build our Dyn= Comp tool to do comparability analysis and type inference </p><p class=3D"M= soPlainText">> of C/C++ programs.=C2=A0 I would like to do the same for = x86 binaries, but </p><p class=3D"MsoPlainText">> I am unsure of the pro= cess to setup a secondary target.</p><p class=3D"MsoPlainText">>=C2=A0</= p><p class=3D"MsoPlainText">Hi Mark</p><p class=3D"MsoPlainText">=C2=A0</p>= <p class=3D"MsoPlainText">What OS are you using?</p><p class=3D"MsoPlainTex= t">=C2=A0</p><p class=3D"MsoPlainText">At the moment I mainly use FreeBSD a= md64, Fedora Linux amd64 and a bit of openSUSE amd64.</p><p class=3D"MsoPla= inText">=C2=A0</p><p class=3D"MsoPlainText">For systems where I have the fu= ll 32bit subsystem installed then all I have to do is run</p><p class=3D"Ms= oPlainText">=C2=A0</p><p class=3D"MsoPlainText">configure.</p><p class=3D"M= soPlainText">=C2=A0</p><p class=3D"MsoPlainText">Autoconf should detect bot= h amd64 and x86 and build both of them.</p><p class=3D"MsoPlainText">=C2=A0= </p><p class=3D"MsoPlainText">So really all that you need to to is to insta= ll the x86 libc. You need the x86 C++ standard lib if you want to run the r= egression tests.</p><p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlai= nText">openSUSE has removed the x86 startup file from gcc so it can no long= er build x86 binaries (it will still run them). So in some cases you may ne= ed to build a compiler for the platform.</p><p class=3D"MsoPlainText">=C2= =A0</p><p class=3D"MsoPlainText">Regards</p><p class=3D"MsoPlainText">=C2= =A0</p><p class=3D"MsoPlainText">Paul</p><p class=3D"MsoPlainText">=C2=A0</= p><p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText">=C2=A0</p><= p class=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoPlainText">______________= _________________________________</p><p class=3D"MsoPlainText">Valgrind-use= rs mailing list</p><p class=3D"MsoPlainText"><a href=3D"mailto:Valgrind-use= [email protected]"><span style=3D"color:windowtext;text-decoration:n= one">[email protected]</span></a></p><p class=3D"MsoPlai= nText"><a href=3D"https://lists.sourceforge.net/lists/listinfo/valgrind-use= rs"><span style=3D"color:windowtext;text-decoration:none">https://lists.sou= rceforge.net/lists/listinfo/valgrind-users</span></a></p></div></body></htm= l> --00000000000074feb006488843b5-- --===============7890445734130181005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============7890445734130181005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users --===============7890445734130181005==--