Re: [lldb-dev] Status of DWARF64 in LLDB

2019-03-12 Thread Eric Christopher via lldb-dev
On Tue, Mar 12, 2019 at 1:43 PM Jan Kratochvil via lldb-dev
 wrote:
>
> On Mon, 11 Mar 2019 21:25:05 +0100, Jan Kratochvil via lldb-dev wrote:
> > I think it is never needed in real world as long as one uses DWP and/or
> > -fdebug-types-section.  Red Hat is using neither (for DWZ postprocessing) 
> > and
> > so I did hit this limit of unsupported DWARF64 in GNU utilities [attached].
>
> FYI chromium-67.0.3396.87.rpm built with gcc-8.3.1-2.fc29.x86_64 DWARF-4
> -fdebug-types-section has 1.6GB .debug_info and 0.5GB .debug_types:
>
> Section Headers:
>   [Nr] Name   Type Address  Off  Size ES Flg Lk 
> Inf Al
>   [30] .debug_aranges PROGBITS    000360   7a7630 00  0   
> 0 16
>   [31] .debug_infoPROGBITS    7a7990 5e358d47 00  0   
> 0  1
>   [32] .debug_abbrev  PROGBITS  5eb006d7  716d053 00  0   
> 0  1
>   [33] .debug_linePROGBITS  65c6d72a  c686a97 00  0   
> 0  1
>   [34] .debug_str PROGBITS  722f41c1 21c96669 01  MS  0   
> 0  1
>   [35] .debug_loc PROGBITS  93f8a82a 24b3a638 00  0   
> 0  1
>   [36] .debug_ranges  PROGBITS  b8ac4e62  ec29fd0 00  0   
> 0  1
>   [37] .debug_types   PROGBITS  c76eee32 1cab0bd3 00  0   
> 0  1
>
FWIW I would consider Chromium a medium sized project...

I'll see if I can grab some sample numbers of a few internal applications.

-eric
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Needs help contributing to lldb-vscode.

2019-03-12 Thread Zachary Turner via lldb-dev
This seems reasonable to me.  It's worth pointing out though that in
regards to the last comment "IMO it's good to make this lldb-vscode more
general so that it can be used by other debugger frontends besides vscode",
despite the name lldb-vscode, there is actually nothing here that is
specific to VSCode.  It reads DAP requests on stdin and responds with DAP
responses on stdout.  That's literally it.  The only thing vscode specific
about it is the names of the source files and some internal classes.  I
actually wouldn't be opposed to changing it to lldb-dap

On Tue, Mar 12, 2019 at 12:34 PM Leonard Mosescu via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Greg, what do you think?
>
>
> On Tue, Mar 12, 2019 at 11:50 AM Qianli Ma  wrote:
>
>> Hi lldb community,
>>
>> I am currently working on a project related to lldb. I'd like to write a
>> DAP RPC server similars to lldb-vscode.cc
>> 
>>  but
>> exports I/O to internal RPC clients. Doing so requires me to reuse some
>> functions defined in lldb-vscode.cc
>> .
>> However as those functions are defined using forward declaration I am not
>> able to do that.
>>
>> I'd like refactor the code a bit. More specifically, I'd like to extract
>> all helper functions in lldb-vscode.cc
>> 
>>  into
>> a separate file and create a header for it.  BTW, IMO it's good to make
>> this lldb-vscode more general so that it can be used by other debugger
>> frontends besides vscode.
>>
>> Please let me know WDYT and how I can proceed to submit changes for
>> review.
>>
>> Thanks and Regards
>> Qianli
>>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Status of DWARF64 in LLDB

2019-03-12 Thread Jan Kratochvil via lldb-dev
On Mon, 11 Mar 2019 21:25:05 +0100, Jan Kratochvil via lldb-dev wrote:
> I think it is never needed in real world as long as one uses DWP and/or
> -fdebug-types-section.  Red Hat is using neither (for DWZ postprocessing) and
> so I did hit this limit of unsupported DWARF64 in GNU utilities [attached].

FYI chromium-67.0.3396.87.rpm built with gcc-8.3.1-2.fc29.x86_64 DWARF-4
-fdebug-types-section has 1.6GB .debug_info and 0.5GB .debug_types:

Section Headers:
  [Nr] Name   Type Address  Off  Size ES Flg Lk Inf 
Al
  [30] .debug_aranges PROGBITS    000360   7a7630 00  0   0 
16
  [31] .debug_infoPROGBITS    7a7990 5e358d47 00  0   0 
 1
  [32] .debug_abbrev  PROGBITS  5eb006d7  716d053 00  0   0 
 1
  [33] .debug_linePROGBITS  65c6d72a  c686a97 00  0   0 
 1
  [34] .debug_str PROGBITS  722f41c1 21c96669 01  MS  0   0 
 1
  [35] .debug_loc PROGBITS  93f8a82a 24b3a638 00  0   0 
 1
  [36] .debug_ranges  PROGBITS  b8ac4e62  ec29fd0 00  0   0 
 1
  [37] .debug_types   PROGBITS  c76eee32 1cab0bd3 00  0   0 
 1


Jan
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Needs help contributing to lldb-vscode.

2019-03-12 Thread Leonard Mosescu via lldb-dev
Greg, what do you think?


On Tue, Mar 12, 2019 at 11:50 AM Qianli Ma  wrote:

> Hi lldb community,
>
> I am currently working on a project related to lldb. I'd like to write a
> DAP RPC server similars to lldb-vscode.cc
> 
>  but
> exports I/O to internal RPC clients. Doing so requires me to reuse some
> functions defined in lldb-vscode.cc
> .
> However as those functions are defined using forward declaration I am not
> able to do that.
>
> I'd like refactor the code a bit. More specifically, I'd like to extract
> all helper functions in lldb-vscode.cc
> 
>  into
> a separate file and create a header for it.  BTW, IMO it's good to make
> this lldb-vscode more general so that it can be used by other debugger
> frontends besides vscode.
>
> Please let me know WDYT and how I can proceed to submit changes for
> review.
>
> Thanks and Regards
> Qianli
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [8.0.0 Release] rc5 has been tagged

2019-03-12 Thread Hans Wennborg via lldb-dev
Dear testers,

8.0.0-rc5 was just tagged from the release_80 branch at r355909.

This is identical to rc4 with the addition of r355743. Hopefully it is the
final release candidate, so please give it a good testing.

As usual, please run the test script, share your results, and upload
binaries.

I'll publish source tarballs and docs as soon as possible, and binaries as
they become available.

Thanks for all your help so far, we're almost there :-)

Cheers,
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev