Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
Okay we're back to green here: http://lab.llvm.org:8080/green/job/lldb_build_test/16173/ Thanks, Enrico! Zachary, I may let this rest until the morning. If you want to try something else, shoot me a patch and I'll gladly try it. -Todd On Mon, Jan 25, 2016 at 9:16 PM, Todd Fiala wrote: > It's

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
It's in item 3 from Effective Python, by Brett Slatkin, which goes over having methods that always go to unicode or to byte streams taking either unicode or byte style strings, for both Python 2 and Python 3. Essentially you figure out what you want it to be in, and you write a couple helper route

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Zachary Turner via lldb-dev
I'm also not sure why Linux isn't failing. Looking at the documentation for io.write https://docs.python.org/2/library/io.html#text-i-o> object, i see this: write(*s*) Write the unicode

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
Hah the comedy of late night emails. We all go away for hours, then all get back here within minutes :-) (Zachary - I will still have a look at it tonight since I am curious why we weren't seeing it on all the (what I think are) Python 2.7-based systems). On Mon, Jan 25, 2016 at 9:02 PM, Enrico

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Enrico Granata via lldb-dev
Should be reverted in 258791. Sent from my iPhone > On Jan 25, 2016, at 8:54 PM, Zachary Turner wrote: > > sorry, yea I stuck around for a while after that patch waiting for emails, > but nothing came through. Please revert in the meantime, I'll work on a fix > tomorrow. > >> On Mon, Jan 25

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
Oh no worries, I borked the builder email on our currently cumbersome multi-step process. They're failing with a permutation of this: Traceback (most recent call last): File "/Users/buildslave/jenkins/sharedspace/lldb@2/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2224, in dsym_test_

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Zachary Turner via lldb-dev
sorry, yea I stuck around for a while after that patch waiting for emails, but nothing came through. Please revert in the meantime, I'll work on a fix tomorrow. On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I think I see what happened w/r/t why no em

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
I think I see what happened w/r/t why no emails when out when the build went heavy red. (Well they went out internally, but not externally). When I made the change on Friday to improve the workflow for the Green Dragon OS X builder and test output, I switched email over to the builder step, which

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
Well our whole test suite just stopped running, so yes. On Mon, Jan 25, 2016 at 6:58 PM, Enrico Granata wrote: > > On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Not sure exactly what it is, but all the tests are failing due to some bad > assumptions

Re: [lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev > wrote: > > Not sure exactly what it is, but all the tests are failing due to some bad > assumptions of unicode vs. str on Python 2 vs. 3 if I had to guess. > Author: zturner Date: Mon Jan 25 18:59:42 2016 New Revision: 258759 URL: htt

[lldb-dev] something just toasted the test suite on OS X

2016-01-25 Thread Todd Fiala via lldb-dev
Not sure exactly what it is, but all the tests are failing due to some bad assumptions of unicode vs. str on Python 2 vs. 3 if I had to guess. I am not going to be able to look at details on that, but here's a link to the log on the OS X builder: http://lab.llvm.org:8080/green/job/lldb_build_test

Re: [lldb-dev] Bad state of release 3.7.1?

2016-01-25 Thread David Jones via lldb-dev
r246756 has a fix, if you are comfortable applying it. It's a large patch. In theory it should back-port but I have not tried it. The API gap from 3.7.1 to 3.8 is quite minimal, so you should be able to get your applications running with 3.8 rather easily if they are running on 3.7.1 already. O

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 4:48 PM, Siva Chandra wrote: > > I think this one: > http://llvm.org/viewvc/llvm-project?view=revision&revision=240578 > > > On Mon, Jan 25, 2016 at 4:34 PM, Enrico Granata >

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
I think this one: http://llvm.org/viewvc/llvm-project?view=revision&revision=240578 On Mon, Jan 25, 2016 at 4:34 PM, Enrico Granata wrote: > > On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > lldb-340.4.119 (OSX 10.11.3) > > On Mon, Jan 25, 2016 at

Re: [lldb-dev] Bad state of release 3.7.1?

2016-01-25 Thread Jeffrey Tan via lldb-dev
Btw: is there a fix that we can cherry pick? Or is it safe for us to build lldb 3.8rc1 with llvm3.7.1? On Mon, Jan 25, 2016 at 4:34 PM, Jeffrey Tan wrote: > Thanks David. > I am new to lldb group but it's kind of surprise to me that the lldb on > the official release page(http://llvm.org/release

Re: [lldb-dev] Bad state of release 3.7.1?

2016-01-25 Thread Jeffrey Tan via lldb-dev
Thanks David. I am new to lldb group but it's kind of surprise to me that the lldb on the official release page(http://llvm.org/releases/download.html#3.7.1) can have such big problems(can't attach/launch). Don't we fully test lldb before we post on the official website? On Mon, Jan 25, 2016 at

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev > wrote: > > lldb-340.4.119 (OSX 10.11.3) > > On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra > wrote: > On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wro

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 4:04 PM, Vadim Chugunov wrote: > > > > On Mon, Jan 25, 2016 at 3:31 PM, Enrico Granata > wrote: > >> >> Whose IsSynthetic() is supposed to return True,- the parent's or the >> child's? > > What do you mean with this? > The model is that y

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
On Mon, Jan 25, 2016 at 4:09 PM, Vadim Chugunov wrote: > lldb-340.4.119 (OSX 10.11.3) I have no idea what that number means. May be Enrico can figure if that build has the fix or not. > On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra > wrote: >> >> On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Vadim Chugunov via lldb-dev
lldb-340.4.119 (OSX 10.11.3) On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra wrote: > On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > > If I have an SBValue for an object whose type has a formatter enabled for > > it, is there a way to detect this via the Python A

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev wrote: > Hi, > If I have an SBValue for an object whose type has a formatter enabled for > it, is there a way to detect this via the Python API, and if so, request an > "unmodified" view of the object? > I've experimented with value.IsS

Re: [lldb-dev] Bad state of release 3.7.1?

2016-01-25 Thread Jeffrey Tan via lldb-dev
Btw: here is the source that we built lldb from: http://llvm.org/releases/download.html#3.7.1 direct link http://llvm.org/releases/3.7.1/lldb-3.7.1.src.tar.xz On Mon, Jan 25, 2016 at 2:37 PM, Jeffrey Tan wrote: > Hi, > > My colleague downloaded and built 3.7.1 version of lldb on Linux. When we

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 3:20 PM, Vadim Chugunov wrote: > > On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata > wrote: > >> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev >> mailto:lldb-dev@lists.llvm.org>> wrote: >> >> Hi, >> If I have an SBValue for an obj

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Vadim Chugunov via lldb-dev
On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata wrote: > > On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Hi, > If I have an SBValue for an object whose type has a formatter enabled for > it, is there a way to detect this via the Python API, and

[lldb-dev] Bad state of release 3.7.1?

2016-01-25 Thread Jeffrey Tan via lldb-dev
Hi, My colleague downloaded and built 3.7.1 version of lldb on Linux. When we used it to attach to a normal process(like sleep), it just hangs forever: bin/lldb -n sleep (lldb) process attach --name "sleep" And my private built 3.8.0 version works fine. Just to confirm, is 3.7.1 a bad version?

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > If I have an SBValue for an object whose type has a formatter enabled for it, > is there a way to detect this via the Python API, and if so, request an > "unmodified" view of the object? There definitely is a way

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

2016-01-25 Thread Hans Wennborg via lldb-dev
This patch looks reasonable to me, but I don't know enough about LLDB to actually review it. +Renato or Pavel maybe? On Thu, Jan 14, 2016 at 11:32 AM, William Dillon via lldb-dev wrote: > Hi again, everyone > > I’d like to ping on this patch now that the 3.8 branch is fairly new, and > merging

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

2016-01-25 Thread Hans Wennborg via lldb-dev
On Sun, Jan 24, 2016 at 2:48 PM, Brian Cain wrote: > > On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain wrote: >> >> On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: >>> >>> >>> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev >>> wrote: SuSE Linux Enterprise Server 11SP3 x86_6

[lldb-dev] [Bug 26289] New: lldb host crashes with allocation failure when attaching to a remote android target

2016-01-25 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=26289 Bug ID: 26289 Summary: lldb host crashes with allocation failure when attaching to a remote android target Product: lldb Version: unspecified Hardware: Other OS: o

Re: [lldb-dev] Ubuntu version-based fail/skip

2016-01-25 Thread Tamas Berghammer via lldb-dev
I think recently we are trying to reduce the number of decorators we are having so adding a few new Ubuntu specific decorators might not be a good idea. My suggestion would be to move on a little bit to the functional programming style with adding a new option to @expetedFailureAll where we can spe

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

2016-01-25 Thread Daniel Sanders via lldb-dev
I have some proper rc1 results now. clang+llvm-3.8.0-rc1-mips-linux-gnu.tar.xz test-release.sh refused to run 'make check-all' because libcxx_tsan failed to configure. This is because the thread sanitizer is not supported on MIPS32. After working around this (patch will follow sh

[lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Vadim Chugunov via lldb-dev
Hi, If I have an SBValue for an object whose type has a formatter enabled for it, is there a way to detect this via the Python API, and if so, request an "unmodified" view of the object? I've experimented with value.IsSynthetic() and value.GetNonSyntheticValue(), but the former seems to always retu