https://bugs.llvm.org/show_bug.cgi?id=44430
Tatyana Krasnukha changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.llvm.org/show_bug.cgi?id=44432
Tatyana Krasnukha changed:
What|Removed |Added
Fixed By Commit(s)||a31130f6fcf27518b31a8ac1f59
https://bugs.llvm.org/show_bug.cgi?id=45112
Bug ID: 45112
Summary: Tests import "lldb.macosx.heap" incorrectly
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Status: NEW
Severity: normal
On Wed, Mar 4, 2020 at 2:49 PM Hans Wennborg wrote:
>
> Hello everyone,
>
> It took a bit longer than planned, but Release Candidate 3 is now
> here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at
> 3a843031a5 and contains 95 commits since the previous release
> candidate.
>
> If no
On Wed, Mar 4, 2020 at 2:49 PM Hans Wennborg wrote:
>
> Hello everyone,
>
> It took a bit longer than planned, but Release Candidate 3 is now
> here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at
> 3a843031a5 and contains 95 commits since the previous release
> candidate.
>
> If no
On Wed, 2020-03-04 at 14:49 +0100, Hans Wennborg via Release-testers
wrote:
> Hello everyone,
>
> It took a bit longer than planned, but Release Candidate 3 is now
> here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at
> 3a843031a5 and contains 95 commits since the previous release
>
Uploaded Ubuntu 18.04 binaries:
7ebc00479d05772e56c34c1b0f40295af2dd4a6b165d9107946ff2cdb7c219ac
clang+llvm-10.0.0-rc3-x86_64-linux-gnu-ubuntu-18.04.tar.xz
On Wed, Mar 4, 2020 at 7:49 AM Hans Wennborg via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> Hello everyone,
>
> It took a bit longer than
Thanks! Added.
On Thu, Mar 5, 2020 at 3:15 PM Brian Cain wrote:
>
> Uploaded Ubuntu 18.04 binaries:
> 7ebc00479d05772e56c34c1b0f40295af2dd4a6b165d9107946ff2cdb7c219ac
> clang+llvm-10.0.0-rc3-x86_64-linux-gnu-ubuntu-18.04.tar.xz
>
> On Wed, Mar 4, 2020 at 7:49 AM Hans Wennborg via llvm-dev
> w
BTW, I think the better way to handle this in lldb is not to move the PC past
the trap when you stop, but that when CONTINUING past a trap that we don't
recognize, we always make sure we start past the trap. That way it won't look
weird when people compare crash logs coming from hitting a trap
That shouldn't be too hard to do. We already have machinery to inject a "step
over breakpoint trap" ThreadPlan when we continue, so we could use the same
detection point to just move the PC before continuing in the case of an
unrecognized trap.
Jim
> On Mar 5, 2020, at 10:10 AM, Jim Ingham v
Glad to hear from you. I am:
jing...@apple.com
Jim
> On Mar 3, 2020, at 10:11 AM, SREENIVASA SUMADITHYA - IIITK via lldb-dev
> wrote:
>
> I wanna work on the open project "Add support for batch-testing to the LLDB
> testsuite." for google summer of code
> Can I get more details on that?
>
11 matches
Mail list logo
