[Bug 241773] lldb does not display external variables properly.

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241773 --- Comment #9 from bc...@lafn.org --- Using (lldb) log enable posix all then run (lldb) p id generates a lot of ptrace entries, however after the p id command, I get: Process 26878 stopped * thread #1, name = 'testprog', stop reason =

[Bug 241773] lldb does not display external variables properly.

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241773 --- Comment #8 from bc...@lafn.org --- Having upgraded to 12.2, I ran the lldb session again. Lldb had degraded significantly. Stepping through the call to testfunc yields the following: 6 7void testfunc(void); 8int

[Bug 241137] Base lldb 9 crashes compared to devel/llvm90

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241137 Dimitry Andric changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 241137] Base lldb 9 crashes compared to devel/llvm90

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241137 --- Comment #4 from Ed Maste --- I think this is resolved now? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list

[Bug 241773] lldb does not display external variables properly.

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241773 --- Comment #7 from Ed Maste --- You can turn on logging in lldb to help figure out what is going on - sorry it has been some time since I've been actively involved in lldb and do not recall the specific channels and categories. To see

[Bug 241773] lldb does not display external variables properly.

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241773 --- Comment #6 from Ed Maste --- Tried to reproduce on -current with lldb version 11.0.0 (g...@github.com:llvm/llvm-project.git revision llvmorg-11.0.0-rc2-0-g414f32a9e86) clang revision llvmorg-11.0.0-rc2-0-g414f32a9e86 llvm revision

[Bug 250702] c++filt crashes on a symbol representing a C++ lambda function

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250702 --- Comment #15 from Ed Maste --- (In reply to Dimitry Andric from comment #14) > That said, it might be more future-proof if we import libcxxabi from > the llvm project into contrib, and start building that, at least > for its demangler

[Bug 250783] ld segmentation fault

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250783 --- Comment #6 from Dimitry Andric --- Ok, to have something to submit to upstream, we need a reproduction case, and lld has an option for this, which produces a tarball: --reproduce= Write a tar file containing input files and

[Bug 250388] unable to make buildworld releng/12.1. clang always crashes

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250388 --- Comment #8 from Alex Richardson --- I believe that backporting this change is very low risk. However it depends on a previous commits being merged too. I do not currently have a setup to do this backporting, but if someone else would

[Bug 250702] c++filt crashes on a symbol representing a C++ lambda function

2020-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250702 --- Comment #14 from Dimitry Andric --- (In reply to Yuri Victorovich from comment #13) Yes, the elftoolchain demangler misses a few more modern features, and its development does not seem very active. (Not necessarily for the other parts