Hello everyone,
9.0.0-rc2 was tagged yesterday from the release_90 branch at r368683.
In the Git monorepo it's available as the llvmorg-9.0.0-rc2 tag.
Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc2
Binaries will be added as they become available.
The tag went in r
https://bugs.llvm.org/show_bug.cgi?id=42995
Bug ID: 42995
Summary: MSVC lldb failed to build, error C3861: 'SetID':
identifier not found
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
https://bugs.llvm.org/show_bug.cgi?id=42995
Raphael Isemann changed:
What|Removed |Added
Severity|enhancement |release blocker
Assignee|lldb-dev@l
A recent change is causing several LLDB tests on Windows to fail and
several more to time out, which I intend to look into.
It appears the timeout period is set to 600 seconds (10 minutes), which
seems excessive and causes the Windows build bot to spend lots of time
waiting. (e.g.,
http://lab.llv
On Wed, Aug 14, 2019 at 11:27 AM Adrian McCarthy via lldb-dev
wrote:
>
> A recent change is causing several LLDB tests on Windows to fail and several
> more to time out, which I intend to look into.
>
> It appears the timeout period is set to 600 seconds (10 minutes), which seems
> excessive and
> On Aug 14, 2019, at 11:26 AM, Adrian McCarthy via lldb-dev
> wrote:
>
> A recent change is causing several LLDB tests on Windows to fail and several
> more to time out, which I intend to look into.
>
> It appears the timeout period is set to 600 seconds (10 minutes), which seems
> excessi
Hi everyone,
I’m Ismail, a compiler engineer intern at Apple. As a part of my internship,
I'm adding Fast Conditional Breakpoints to LLDB, using code patching.
Currently, the expressions that power conditional breakpoints are lowered
to LLVM IR and LLDB knows how to interpret a subset of it. If t
> On Aug 14, 2019, at 1:41 PM, Adrian Prantl via lldb-dev
> wrote:
>
>
>
>> On Aug 14, 2019, at 11:26 AM, Adrian McCarthy via lldb-dev
>> wrote:
>>
>> A recent change is causing several LLDB tests on Windows to fail and several
>> more to time out, which I intend to look into.
>>
>> It
On 8/14/19 3:52 PM, Ismail Bennani via lldb-dev wrote:
> Hi everyone,
>
> I’m Ismail, a compiler engineer intern at Apple. As a part of my internship,
> I'm adding Fast Conditional Breakpoints to LLDB, using code patching.
>
> ...
>
> Since all the registers are already mapped to a structure, I sh
On Wed, Aug 14, 2019 at 2:47 PM Jim Ingham wrote:
>
>
> > On Aug 14, 2019, at 1:41 PM, Adrian Prantl via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> >
> >
> >> On Aug 14, 2019, at 11:26 AM, Adrian McCarthy via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >>
> >> A recent change is causin
As a workaround, assuming you're running the tests with lit, you
should be able to override the timeout with --max-time.
On Wed, Aug 14, 2019 at 4:15 PM Adrian McCarthy via lldb-dev
wrote:
>
>
>
> On Wed, Aug 14, 2019 at 2:47 PM Jim Ingham wrote:
>>
>>
>>
>> > On Aug 14, 2019, at 1:41 PM, Adrian
I don't know where the windows bot output is...
Which tests are timing out?
Maybe you ought to skip those tests on Windows for now to reduce the noise?
Jim
> On Aug 14, 2019, at 4:14 PM, Adrian McCarthy wrote:
>
>
>
> On Wed, Aug 14, 2019 at 2:47 PM Jim Ingham wrote:
>
>
> > On Aug
https://bugs.llvm.org/show_bug.cgi?id=42981
mryusolo changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WONTFIX
https://bugs.llvm.org/show_bug.cgi?id=42981
Jonas Devlieghere changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.llvm.org/show_bug.cgi?id=43001
Bug ID: 43001
Summary: lldb can not launch process on android
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
15 matches
Mail list logo
