Andrew Kelley via llvm-dev
2018-Apr-05 21:13 UTC
[llvm-dev] can valgrind read LLD's debug info?
I just filed https://bugs.llvm.org/show_bug.cgi?id=37021 There was another bug that seems related to this which is https://bugs.llvm.org/show_bug.cgi?id=35032 but that one is marked fixed. But this seems to be an issue in trunk. Is this a known issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180405/c0556f8b/attachment.html>
Shoaib Meenai via llvm-dev
2018-Apr-05 21:16 UTC
[llvm-dev] can valgrind read LLD's debug info?
It's more of a valgrind issue than an LLD issue, but you can work around it by linking with --no-rosegment From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Andrew Kelley via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Andrew Kelley <superjoe30 at gmail.com> Date: Thursday, April 5, 2018 at 2:14 PM To: LLVM Dev <llvm-dev at lists.llvm.org> Subject: [llvm-dev] can valgrind read LLD's debug info? I just filed https://bugs.llvm.org/show_bug.cgi?id=37021<https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.llvm.org_show-5Fbug.cgi-3Fid-3D37021&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=LOIzu9sn31pmykUwYH1_wAigCpxv33qUDNdmOrmGop4&s=2_EmscX6fjQZR0pF1CQWKUPDgpBLCJhFfnOvlkivJBE&e=> There was another bug that seems related to this which is https://bugs.llvm.org/show_bug.cgi?id=35032<https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.llvm.org_show-5Fbug.cgi-3Fid-3D35032&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=LOIzu9sn31pmykUwYH1_wAigCpxv33qUDNdmOrmGop4&s=c8bjnWV_NwOLITc1Tc5dCjJC88BhCt86girLjAbXTbk&e=> but that one is marked fixed. But this seems to be an issue in trunk. Is this a known issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180405/aa2c4300/attachment.html>
Andrew Kelley via llvm-dev
2018-Apr-05 21:28 UTC
[llvm-dev] can valgrind read LLD's debug info?
As a frontend, what are the downsides of enabling --no-rosegment by default? So far the pro list is: * valgrind debug info will work by default What's on the con list? On Thu, Apr 5, 2018 at 5:16 PM, Shoaib Meenai <smeenai at fb.com> wrote:> It's more of a valgrind issue than an LLD issue, but you can work around > it by linking with --no-rosegment > > > > *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Andrew > Kelley via llvm-dev <llvm-dev at lists.llvm.org> > *Reply-To: *Andrew Kelley <superjoe30 at gmail.com> > *Date: *Thursday, April 5, 2018 at 2:14 PM > *To: *LLVM Dev <llvm-dev at lists.llvm.org> > *Subject: *[llvm-dev] can valgrind read LLD's debug info? > > > > I just filed https://bugs.llvm.org/show_bug.cgi?id=37021 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.llvm.org_show-5Fbug.cgi-3Fid-3D37021&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=LOIzu9sn31pmykUwYH1_wAigCpxv33qUDNdmOrmGop4&s=2_EmscX6fjQZR0pF1CQWKUPDgpBLCJhFfnOvlkivJBE&e=> > > There was another bug that seems related to this which is > https://bugs.llvm.org/show_bug.cgi?id=35032 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.llvm.org_show-5Fbug.cgi-3Fid-3D35032&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=LOIzu9sn31pmykUwYH1_wAigCpxv33qUDNdmOrmGop4&s=c8bjnWV_NwOLITc1Tc5dCjJC88BhCt86girLjAbXTbk&e=> > but that one is marked fixed. But this seems to be an issue in trunk. > > Is this a known issue? >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180405/e7c4fb01/attachment.html>