[lldb-dev] FYI: a python crash running tests

[Ted Woodward via lldb-dev]

Yes, it’s up for review. Please see http://reviews.llvm.org/D17860 .

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: Adrian McCarthy [mailto:amccarth at google.com] 
Sent: Tuesday, March 08, 2016 11:34 AM
To: Ted Woodward
Cc: Zachary Turner; LLDB
Subject: Re: FYI: a python crash running tests

 

Did you ever push a fix?  I'm still seeing this problem, even after a fresh sync.

 

I'm happy to take a look at it today if you don't already have a fix.

 

On Thu, Mar 3, 2016 at 10:18 AM, Ted Woodward <ted.woodward at codeaurora.org <mailto:ted.woodward at codeaurora.org> > wrote:

I think I see the problem; I’ll push up a fix.

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: Zachary Turner [mailto:zturner at google.com <mailto:zturner at google.com> ] 
Sent: Thursday, March 03, 2016 11:54 AM
To: Adrian McCarthy; LLDB; Ted Woodward
Subject: Re: FYI: a python crash running tests

 

Hi Ted, any chance this is your recent change? I know you had some changes in this file recently

On Wed, Mar 2, 2016 at 4:46 PM Adrian McCarthy <amccarth at google.com <mailto:amccarth at google.com> > wrote:

Running ninja check-lldb now has one crash in a Python process, due to deferencing a null pointer in IRExecutionUnit.cpp:  candidate_sc.symbol is null, which leads to a call with a null this pointer.

 

However, the Test Result Summary shows no problems:  0 failures, errors, exceptional exits, and timeouts.

 

I would try to debug it, but I'm about to head out.

 

Adrian.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160308/ca09a7d8/attachment.html>