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:
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 i
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 be
> 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 thi
On 10/01/2019 17:16, Peng Yu via lldb-dev wrote:
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 goo
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 figur
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 being significantly better in other ways (for example,
there was a test that took
