Displaying 7 results from an estimated 7 matches for "glldb".
Did you mean:
lldb
2018 Jun 13
4
[lldb-dev] Adding DWARF5 accelerator table support to llvm
...ducer/consumer of these
tables which is independent of llvm, I'd like to know whether we are
compatible with it.
I'd also like to make the new functionality more easily accessible to
users. I am not sure what our policy here is, but I was thinking of
either including this functionality in -glldb (on non-apple targets);
or by adding a separate -g flag for it (-gdebug-names-section?), with
the goal of eventual inclusion into -glldb. I exclude apple targets
because: a) they already have a thing that works and the lack of
.apple_objc would be a pessimization; b) the different debug info
distri...
2018 Jan 17
6
Adding DWARF5 accelerator table support to llvm
...1. add .debug_names support to llvm-dwarfdump via the DebugInfo
library (to enable testing of the table generation)
2. add .debug_names generation support (not enabled by default)
3. add .debug_names support to lldb
4. validate all three things work together
5. hook up .debug_names to clang's -glldb flag.
6. add .debug_names support to lld (accelerator table merging)
Right now I have (1) roughly implemented, and I think I'll be able to
put it up for review in a couple of days (although I expect the review
will go through several revisions before being accepted). I also have
a very basic i...
2018 Jan 17
0
Adding DWARF5 accelerator table support to llvm
...ort to llvm-dwarfdump via the DebugInfo
> library (to enable testing of the table generation)
> 2. add .debug_names generation support (not enabled by default)
> 3. add .debug_names support to lldb
> 4. validate all three things work together
> 5. hook up .debug_names to clang's -glldb flag.
> 6. add .debug_names support to lld (accelerator table merging)
>
> Right now I have (1) roughly implemented, and I think I'll be able to
> put it up for review in a couple of days (although I expect the review
> will go through several revisions before being accepted). I...
2018 Jan 30
1
[lldb-dev] Adding DWARF5 accelerator table support to llvm
On Wed, 17 Jan 2018 17:13:36 +0100, Pavel Labath via lldb-dev wrote:
> so I'm writing this email to see if there's anyone
> else interested in this topic, and to try to synchronize our efforts.
I am sure interested in DWARF-5 .debug_names. I wrote its producer+consumer
for GDB (but not producing/using DW_IDX_DIE_offset as GDB cannot use it).
> 1. add .debug_names support to
2020 Nov 06
0
[lldb] Error - Failed to launch or debug process
Using OpenBSD clang v10.0.1 targeting aarch64-unknown-openbsd6.8 to compile
a simple SDL c program using the following clang command to do so:
clang -glldb -std=c99 -Wall -Werror$(pkg-config --cflags --libs sdl2) example.c -o example
No errors or warnings compiling. I attempt to debug 'example' with lldb v10.0.1:
lldb example
Set my breakpoints:
(lldb) breakpoint set --name main
set the command to be performed at the breakpoint created:...
2018 Jan 17
2
Adding DWARF5 accelerator table support to llvm
...p via the DebugInfo
>> library (to enable testing of the table generation)
>> 2. add .debug_names generation support (not enabled by default)
>> 3. add .debug_names support to lldb
>> 4. validate all three things work together
>> 5. hook up .debug_names to clang's -glldb flag.
>> 6. add .debug_names support to lld (accelerator table merging)
>>
>> Right now I have (1) roughly implemented, and I think I'll be able to
>> put it up for review in a couple of days (although I expect the review
>> will go through several revisions befor...
2018 Jun 13
2
[lldb-dev] Adding DWARF5 accelerator table support to llvm
...l consumer but it ignores the accelerator tables so I don’t expect any issues there.
>
>> I'd also like to make the new functionality more easily accessible to
>> users. I am not sure what our policy here is, but I was thinking of
>> either including this functionality in -glldb (on non-apple targets);
>> or by adding a separate -g flag for it (-gdebug-names-section?), with
>> the goal of eventual inclusion into -glldb. I exclude apple targets
>> because: a) they already have a thing that works and the lack of
>> .apple_objc would be a pessimization...