[lldb-dev] [Bug 40287] New: lldb cannot debug an i386 elf (32 bit) executable on an amd64 platform, (FreeBSD 11.1 and 11.2)

2019-01-10 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=40287 Bug ID: 40287 Summary: lldb cannot debug an i386 elf (32 bit) executable on an amd64 platform, (FreeBSD 11.1 and 11.2) Product: lldb Version: 6.0 Hardware: PC OS:

[lldb-dev] LLVM git monorepo mirror published

2019-01-10 Thread James Y Knight via lldb-dev
The new official monorepo is published to LLVM's github organization, at: https://github.com/llvm/llvm-project. At this point, the repository should be considered stable -- there won't be any more rewrites which invalidate commit hashes (barring some _REALLY_ good reason...). The import process

Re: [lldb-dev] RFC: Simplifying SymbolFile interface

2019-01-10 Thread Davide Italiano via lldb-dev
On Thu, Jan 10, 2019 at 12:43 AM Pavel Labath via lldb-dev wrote: > > On 09/01/2019 20:59, Zachary Turner via lldb-dev wrote: > > The Native PDB symbol file plugin I think is mostly complete. It's at > > least almost as good as the old Windows-only PDB plugin in 90% of ways, > > while actually

Re: [lldb-dev] Figure our what global and static variables are accessed by what functions (at runtime)

2019-01-10 Thread Peng Yu via lldb-dev
> Normally, a CPU only allows a very small (as in, ~4) watchpoints. So I > think this strategy is bound to fail. Thanks. I see there only 4 hardware watchpoints are supported on my machine. Is there a way to set software watchpoints? > If you really need dynamic information about this sort of

[lldb-dev] Figure our what global and static variables are accessed by what functions (at runtime)

2019-01-10 Thread Peng Yu via lldb-dev
Hi, I think that I can use the watchpoint command to set watchpoints on all global and static variables. Then run the lldb and parse the screen output to see what global and static variables are read/write-accessed by what functions. Is this a good strategy? Is there any other better ways to