Re: dwarf2 today on 13-CURRENT

From: Oliver Pinter <oliver.pinter_at_hardenedbsd.org>
Date: Sat, 12 Jan 2019 20:26:14 +0100
On 1/12/19, Oliver Pinter <oliver.pinter_at_hardenedbsd.org> wrote:
> On 1/12/19, Dimitry Andric <dim_at_freebsd.org> wrote:
>> On 12 Jan 2019, at 19:40, Oliver Pinter <oliver.pinter_at_hardenedbsd.org>
>> wrote:
>>> According the following comment in ${SRCTOP}/sys/conf/kern.mk:
>>>
>>> #
>>> # Add -gdwarf-2 when compiling -g. The default starting in clang v3.4
>>> # and gcc 4.8 is to generate DWARF version 4. However, our tools don't
>>> # cope well with DWARF 4, so force it to genereate DWARF2, which they
>>> # understand. Do this unconditionally as it is harmless when not needed,
>>> # but critical for these newer versions.
>>> #
>>> .if ${CFLAGS:M-g} != "" && ${CFLAGS:M-gdwarf*} == ""
>>> CFLAGS+=        -gdwarf-2
>>> .endif
>>>
>>> this dwarf2 limitation still exists in today's HEAD?
>>>
>>> I mean the FreeBSD project switched to elftoolchain and mostly to LLVM
>>> tools. LLDB is compiled by default on 13-CURRENT (~ HEAD) and the kgdb
>>> has moved under the libexec directory, to hide them from the common
>>> usage.
>>
>> See https://reviews.freebsd.org/D17930, where there is a proposed patch
>> for this very topic.
>
> Thanks!
>
> From the other side, is there any result from the GSoC14's klldb?
> I can't really find any info in the project's github branch, but I've found
> this
> patch: https://reviews.llvm.org/rLLDB314672 .

And probably found them: https://reviews.llvm.org/D10216 .

>
>
>
>>
>> -Dimitry
>>
>>
>
Received on Sat Jan 12 2019 - 18:26:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:19 UTC