search for: debuglink

...351934 351946 351947 351948 In a git mirror, it's trivial to find these commits with the following command: git log $(git merge-base origin/release_80 master)..master tools/llvm-objcopy/COFF test/tools/llvm-objcopy/COFF Among these commits, there's one cycle of "Implement --add-gnu-debuglink", "Revert 'Implement --add-gnu-debuglink'", "Reapply: Implement --add-gnu-debuglink", "Remove testcase debugging lines. NFC.". If you prefer, you can pick all of them to keep it similar to trunk, or you can just pick the first one of them, since the la...

...ts. I don't have access to a ppc64be setup to test on, but I've tried to build and run in a setup very similar to the one on the aarch64 buildbot, but I can't reproduce the errors there. The failing test was present in SVN r351801 to r351810, in test/tools/llvm-objcopy/COFF/add-gnu-debuglink.test. The failing test looked like this: http://lab.llvm.org:8011/builders/clang-ppc64be-linux/builds/29113/steps/ninja%20check%201/logs/FAIL%3A%20LLVM%3A%3Aadd-gnu-debuglink.test http://lab.llvm.org:8011/builders/clang-cmake-armv8-quick/builds/9987/steps/ninja%20check%201/logs/FAIL%3A%20LLVM%3A%...

On Tue, 15 Jan 2019, Hans Wennborg wrote: > On Sat, Jan 12, 2019 at 12:49 AM Jordan Rupprecht <rupprecht at google.com> wrote: >> >> >> >> On Fri, Jan 11, 2019 at 6:26 AM Martin Storsjö <martin at martin.st> wrote: >>> >>> Hi, >>> >>> The COFF support in llvm-objcopy is in a pretty half-finished state at the >>>

I am looking to create a tool that can add Apple or DWARF5 accelerator tables to fully linked executables that contain DWARF. This will help us benchmark how much accelerator tables can improve the debugging experience as debuggers don't need to manually index all of the debug info during debugging. Looking at how accelerator tables are currently emitted, they seem to be built up as DWARF is

...xt). Also, no AsmPrinter objects are used in this codebase either. > > llvm-objcopy supports various ad-hoc binary manipulation features where each feature does a very > simple task. Neither llvm-objcopy nor GNU objcopy knows DWARF. --strip-debug, > --compress-debug-sections, --add-gnu-debuglink and --only-keep-debug have "debug" in their names but > these features don't need to parse DWARF. (GNU objcopy has a --debugging but that only works for > a.out and coff, not elf). > > Do we have a more suitable tool for such debugging functionality? dsymutil for ELF? ds...

...AsmPrinter objects are used in this codebase either. > > > llvm-objcopy supports various ad-hoc binary manipulation features where > each feature does a very > simple task. Neither llvm-objcopy nor GNU objcopy knows DWARF. > --strip-debug, > --compress-debug-sections, --add-gnu-debuglink and --only-keep-debug have > "debug" in their names but > these features don't need to parse DWARF. (GNU objcopy has a --debugging > but that only works for > a.out and coff, not elf). > > Do we have a more suitable tool for such debugging functionality? dsymutil &gt...

...in this codebase either. >> >> >> llvm-objcopy supports various ad-hoc binary manipulation features where >> each feature does a very >> simple task. Neither llvm-objcopy nor GNU objcopy knows DWARF. >> --strip-debug, >> --compress-debug-sections, --add-gnu-debuglink and --only-keep-debug have >> "debug" in their names but >> these features don't need to parse DWARF. (GNU objcopy has a --debugging >> but that only works for >> a.out and coff, not elf). >> >> Do we have a more suitable tool for such debugging fun...

...utils\TableGen && CMAKE_OBJCOPY-NOTFOUND --only-keep-debug C:/code/clang-builder/build/instrumented/bin/llvm-tblgen.exe C:/code/clang-builder/build/instrumented/bin/llvm-tblgen.exe.debug && CMAKE_STRIP-NOTFOUND -gx C:/code/clang-builder/build/instrumented/bin/llvm-tblgen.exe -R .gnu_debuglink && CMAKE_OBJCOPY-NOTFOUND --add-gnu-debuglink=C:/code/clang-builder/build/instrumented/bin/llvm-tblgen.exe.debug C:/code/clang-builder/build/instrumented/bin/llvm-tblgen.exe"" LINK: command "C:\code\clang-builder\src\bootstrap\bin\lld-link.exe /nologo utils\TableGen\CMakeFile...

Hey everyone! Objcopy is a powerful tool that allows one to modify object files in various manners, for example, modify symbols / symbol tables or copy / remove particular parts of a binary. It also serves as a basis for the strip tool. Currently, llvm-objcopy only supports ELF files while binutils' objcopy can handle Mach-O files as well. Besides extending the existing tool to support Mach-O

...;>> >>> >>> llvm-objcopy supports various ad-hoc binary manipulation features where >>> each feature does a very >>> simple task. Neither llvm-objcopy nor GNU objcopy knows DWARF. >>> --strip-debug, >>> --compress-debug-sections, --add-gnu-debuglink and --only-keep-debug >>> have "debug" in their names but >>> these features don't need to parse DWARF. (GNU objcopy has a --debugging >>> but that only works for >>> a.out and coff, not elf). >>> >>> Do we have a more suitable too...

Hey everyone, Sorry to jump in on this so late. My two cents is that it should remain GNU objoppy compatible most likely. It was always vaguely a desire to have command line compatibility but it has turned out over time that this is actually a crucial feature and should be one of the top priorities. You can't just go into a giant build system and swap out all the uses of GNU objcopy with

Hi James, Thank you for the comments. >I think we're not terribly far from that ideal, now, for ELF. Maybe only these three things need to be done? -- >  1. Teach lld how to emit a separated debuginfo output file directly, without requiring an objcopy step. >  2. Integrate DWARFLinker into lld. >  3. Create a new tool which takes the separated debuginfo and DWO/DWP files