Timothee, do you intend to work on this?
What can I do to help?
In the meanwhile, I'd appreciate it if someone could take a look at
https://reviews.llvm.org/D24794 (currently, debugging D code is very much
broken without that change).
-Johan
On Thu, Sep 22, 2016 at 7:21 PM, Greg Clayton via lld
https://llvm.org/bugs/show_bug.cgi?id=12355
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15719
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15036
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15591
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15936
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=16000
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17096
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17227
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17385
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17189
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17628
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15302
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=18064
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=30526
Bug ID: 30526
Summary: deadlock when calling SBThread::GetSelectedFrame
Product: lldb
Version: 3.9
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=18077
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=18579
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=18965
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19248
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19245
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19695
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19783
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19818
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=19826
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20143
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20203
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20233
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20319
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20352
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20687
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
Just did, and it looks good.
> On Sep 26, 2016, at 3:49 AM, Johan Engelen wrote:
>
> Timothee, do you intend to work on this?
> What can I do to help?
>
> In the meanwhile, I'd appreciate it if someone could take a look at
> https://reviews.llvm.org/D24794 (currently, debugging D code is very
Dear All,
Today some of you received dozen e-mails from YouTrack connected with
something which looks like LLVM PRs. Please ignore them and I do
apologize that you received them.
Here is some background. As you may know we had a lot of problems with
Bugzilla recently due to spam activity. Current
On 26 September 2016 at 19:12, Anton Korobeynikov via llvm-dev
wrote:
> Note that nothing was decided yet, it might be very probable that
> we'll continue use Bugzilla, we're just evaluating other options and
> collecting the relevant information. We will try to make sure that
> there will be no m
33 matches
Mail list logo