on Molenda; lldb-commits@lists.llvm.org
Subject: Re: [Lldb-commits] FreeBSD kernel debugging fixes
I am worried that this will adversely affect the normal DWARF that is in ELF
files. What does typical DWARF look like when all of the file addresses in
DWARF and the symtab are set correctly to uniq
something within a module.
>
> -- Brian
>
> From: Jason Molenda [jmole...@apple.com]
> Sent: Wednesday, September 20, 2017 4:18 PM
> To: Koropoff, Brian
> Cc: lldb-commits@lists.llvm.org
> Subject: Re: [Lldb-commits] FreeBSD kernel debu
Wednesday, September 20, 2017 4:18 PM
To: Koropoff, Brian
Cc: lldb-commits@lists.llvm.org
Subject: Re: [Lldb-commits] FreeBSD kernel debugging fixes
Right, we always record symbol addresses as the offset to the section that
contains them. The Address class in lldb is used everywhere for this. The
> https://github.com/llvm-mirror/lldb/blob/master/include/lldb/API/SBModule.h#L120
>
> Regards,
> Brian Koropoff
> Dell EMC
>
>
> From: Jason Molenda [jmole...@apple.com]
> Sent: Wednesday, September 20, 2017 3:47 PM
> To: Koropoff, Brian
> Cc: lldb-commits@lists.llvm
Molenda [jmole...@apple.com]
Sent: Wednesday, September 20, 2017 3:47 PM
To: Koropoff, Brian
Cc: lldb-commits@lists.llvm.org
Subject: Re: [Lldb-commits] FreeBSD kernel debugging fixes
Regarding the overlapping files -- when lldb first loads multiple binaries (but
does not have a running process), it doe
Regarding the overlapping files -- when lldb first loads multiple binaries (but
does not have a running process), it doesn't know where to set the load
addresses of these binaries so they are all 0-based (or if they have a
specified load address in the object file, at that address).
We rely on
