Displaying 5 results from an estimated 5 matches for "gdebug".
Did you mean:
debug
2018 Jun 13
4
[lldb-dev] Adding DWARF5 accelerator table support to llvm
...ke 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
distribution model means it requires more testing and code (dsymutil).
For oth...
2017 Sep 08
2
Status of debuginfo-tests
...we need the flexibility to test both independently of each other.
On a posixy platform, you only care the compiler and don't care what the
linker is. On the other hand, it has its own set of unique aspects. You
might decide to compile and link many times, so that you can test
-gsplit-dwarf, -gdebug-info-kind=limited, -gdebug-info-kind=full,
-gdb-index, etc. against a single program.
I don't see a useful abstraction that glosses over these differences that
isn't a ton of work for minimal gain, given the frequency with which we'd
need to fall back to a custom test anyway.
---------...
2017 Sep 07
2
Status of debuginfo-tests
I was thinking of something along the lines of:
// SCRIPT-POSIX: posix/aggregate-indirect-arg.s
// SCRIPT-WIN: win/aggregate-indirect-arg.s
class SVal {
public:
~SVal() {}
const void* Data;
unsigned Kind;
};
void bar(SVal &v) {}
class A {
public:
void foo(SVal v) { bar(v); }
};
int main() {
SVal v;
v.Data = 0;
v.Kind = 2142;
A a;
a.foo(v);
return 0;
}
Then, you could
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
2018 Jun 13
2
[lldb-dev] Adding DWARF5 accelerator table support to llvm
...ere.
>
>> 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
>> distribution model means it requires more...