RetroSearch Browse

Mon Jul 6 08:21:06 PDT 2020 · https://lists.llvm.org/pipermail/llvm-dev/2020-July/143102.html

Another solution is to build the entire program with debug info, then write
a small shell sscript which crawls your tree using objcopy or something to
strip out the debug symbols, then re-run your build step.  It should see
the object files as not being out of date since they are newer than the
source files, but the final executable being out of date since the object
files are newer than the executable.  So it should simply re-link with
debug info stripped out of whichever files you ran objcopy on.  This has
the nice property that you don't have to make local changes to cmake, and
you can keep this script somewhere in your local repository.

On Mon, Jul 6, 2020 at 7:34 AM John Paul Adrian Glaubitz via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi Alexey!
>
> On 7/6/20 4:13 PM, Alexey Zhikhartsev wrote:
> > This should help:
> > http://lists.llvm.org/pipermail/llvm-dev/2019-August/134606.html
> Thanks. Exactly what I was looking for.
>
> Kind Regards,
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaubitz at debian.org
> `. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
>   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200706/7163ac70/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://lists.llvm.org/pipermail/llvm-dev/2020-July/143102.html below:

[llvm-dev] Enabling debug information for debug only