[lldb-dev] [Bug 26437] New: TestProcessIO.test_stdin_redirection is flaky on android

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=26437

Bug ID: 26437
   Summary: TestProcessIO.test_stdin_redirection is flaky on
android
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: lab...@google.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

(At least) in build 5110 of the ubuntu->android buildbot it failed the start
the inferior.

==
FAIL: test_stdin_redirection_dwo (TestProcessIO.ProcessIOTestCase)
Exercise SBLaunchInfo::AddOpenFileAction() for STDIN without specifying
STDOUT or STDERR.
--
Traceback (most recent call last):
  File
"/home/lldb_build/lldbSlave/lldb-cross-compile/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 2299, in dwo_test_method
return attrvalue(self)
  File
"/home/lldb_build/lldbSlave/lldb-cross-compile/llvm/tools/lldb/packages/Python/lldbsuite/test/python_api/process/io/TestProcessIO.py",
line 47, in test_stdin_redirection
self.run_process(False)
  File
"/home/lldb_build/lldbSlave/lldb-cross-compile/llvm/tools/lldb/packages/Python/lldbsuite/test/python_api/process/io/TestProcessIO.py",
line 165, in run_process
self.assertTrue(error.Success(), "Make sure process launched successfully")
AssertionError: False is not True : Make sure process launched successfully
Config=aarch64-/home/lldb_build/Toolchains/aarch64-21/bin/aarch64-linux-android-gcc

The logs seems to indicate that the server returned an error response to the $A
packet. It is hard to diagnose the exact error without access to the server
logs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 26439] New: android adb connection can sometimes fail

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=26439

Bug ID: 26439
   Summary: android adb connection can sometimes fail
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: lab...@google.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

I have observed this happen on the darwin->android buildbot, build #8401


==
FAIL: test_c_global_variables_dwo (TestGlobalVariables.GlobalVariablesTestCase)
   Test 'frame variable --scope --no-args' which omits args and shows scopes.
--
Traceback (most recent call last):
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 2299, in dwo_test_method
return attrvalue(self)
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 617, in wrapper
func(*args, **kwargs)
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 617, in wrapper
func(*args, **kwargs)
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lang/c/global_variables/TestGlobalVariables.py",
line 44, in test_c_global_variables
'stop reason = breakpoint'])
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 2677, in expect
self.runCmd(str, msg=msg, trace = (True if trace else False), check = not
error, inHistory=inHistory)
  File
"/Users/lldb_build/lldbSlave/buildDir/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 2603, in runCmd
msg if msg else CMD_MSG(cmd))
AssertionError: False is not True : Process should be stopped due to breakpoint
Config=aarch64-/Users/lldb_build/Toolchains/aarch64-21/bin/aarch64-linux-android-gcc


Logs are a bit scarce, but they seem to indicate this was caused by a failed
adb connection while attempting to install liba.so.
1454384745.166052000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::ConnectionFileDescriptor ()
1454384745.166061000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::Connect (url = 'connect://localhost:5037')
1454384745.166066000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::CloseCommandPipe()
1454384745.166078000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::OpenCommandPipe() - success readfd=16 writefd=17
1454384745.166085000 [ced5/0713]: Socket::TcpConnect (host/port =
localhost:5037)
1454384745.166098000 [ced5/0713]: TCPSocket::Connect (host/port =
localhost:5037)
1454384745.166318000 [ced5/0713]: 0x7fcfec5099d0 Socket::Close (fd = 18)
1454384745.166341000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::~ConnectionFileDescriptor ()
1454384745.166348000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::Disconnect ()
1454384745.166353000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::Disconnect(): Nothing to disconnect
1454384745.166359000 [ced5/0713]: 0x7fff5a6affd0
ConnectionFileDescriptor::CloseCommandPipe()
1454384745.166379000 [ced5/0713]: SBTarget(0x7fcfee005400)::Launch (...) =>
SBProcess(0x7fcfef82ea00)

Normally, the TCPSocket::Connect should be followed by a bunch of socket
traffic. Instead, we seem to be closing the socket without sending any data.

It's hard to tell what to do at the moment, but I'll try to add more logging to
better understand the problem..

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] more Green Dragon OS X buildbot/testbot tweaks

[Todd Fiala via lldb-dev]

Hi all,

I don't have this perfectly configured yet.  It is happily running builds
and running test suites.  However, while it reports test failures just
fine, it doesn't fail the build on a test failure.  I'm tracking down why
now.  I have just adjusted something so that we get an email on test
failures.  (We had three sho up on OS X yesterday that are getting logged
at lab.llvm.org:8080 but are not actually failing the build).

-- 
-Todd
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] more Green Dragon OS X buildbot/testbot tweaks

[Todd Fiala via lldb-dev]

I have the OS X testbot fail nag emails going out properly now.

Thanks!

-Todd

On Tue, Feb 2, 2016 at 7:58 AM, Todd Fiala  wrote:

> Hi all,
>
> I don't have this perfectly configured yet.  It is happily running builds
> and running test suites.  However, while it reports test failures just
> fine, it doesn't fail the build on a test failure.  I'm tracking down why
> now.  I have just adjusted something so that we get an email on test
> failures.  (We had three sho up on OS X yesterday that are getting logged
> at lab.llvm.org:8080 but are not actually failing the build).
>
> --
> -Todd
>



-- 
-Todd
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 26441] New: TestConsecutiveBreakpoints.test_single_step_thread_specific fails on OSX

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=26441

Bug ID: 26441
   Summary: TestConsecutiveBreakpoints.test_single_step_thread_spe
cific fails on OSX
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: lab...@google.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

FAIL: test_single_step_thread_specific
(TestConsecutiveBreakpoints.ConsecutiveBreakpointsTestCase)
   Test that single step stops, even though the second breakpoint is not valid.
--
Traceback (most recent call last):
  File
"/Users/buildslave/jenkins/sharedspace/lldb@2/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 552, in wrapper
return func(self, *args, **kwargs)
  File
"/Users/buildslave/jenkins/sharedspace/lldb@2/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py",
line 96, in test_single_step_thread_specific
self.bkpt_address.GetLoadAddress(self.target))
AssertionError: 4497530763L != 4497530757L


It is not yet clear why r259488 (which fixed the issue on linux and added the
test) does not work on osx.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb status at windows

[Red Skotina via lldb-dev]

i found reson of hang. im used https://github.com/adoxa/ansicon for color
console.
after uninstall it is now work as expected.


2016-01-23 22:59 GMT+03:00 Red Skotina :

> im rebuild lldb as x64 application and reabuild my test application with
> x64 llvm.
> at first look same.
> But when my internet was breaked at some moment application under lldb run
> and finish correct.
> It is like some magic with my pc.
> When i have acces to internet lldb hangs, when i disable my internet - it
> is correct finished.
> I try examine this behavior and determine finite conditions for hangs.
>
> 2016-01-23 19:27 GMT+03:00 Zachary Turner :
>
>> I'm out of office until Monday, but I'll try to reproduce this then and
>> update.  Never seen a hang before, so I wonder if there's something
>> different about your machine that we haven't thought of or taken into
>> account.  Either way I'll update Monday.
>>
>> On Sat, Jan 23, 2016 at 12:57 AM Red Skotina 
>> wrote:
>>
>>> same.
>>>
>>> d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp
>>>
>>> d:\code\Unity_Unpacker\tests\test2>lldb a.exe
>>> (lldb) target create "a.exe"
>>> Current executable set to 'a.exe' (i686).
>>> (lldb) run
>>>
>>> Process 6984 launching
>>> ---
>>> hangs
>>>
>>> 2016-01-23 11:54 GMT+03:00 Zachary Turner :
>>>
 Ahh you probably need to add -g to clang, otherwise it's not generating
 debug info.  I've never tried debugging a binary with no debug info.
 Obviously it shouldn't hang, but either way it's just not something we've
 tested on Windows.



 On Sat, Jan 23, 2016 at 12:51 AM Red Skotina 
 wrote:

> yes. i doing it. you can see what clang use
> d:\\code\\llvm\\build\\bin\\lld-link.exe
> but anyway it is hang :(
>
> 2016-01-22 23:30 GMT+03:00 Zachary Turner :
>
>> Under llvm/tools also checkout lld.  So your directories should look
>> like this:
>>
>> llvm
>> \-- tools
>> \-- clang
>> \-- lldb
>> \-- lld
>>
>> Then re-run cmake to generate build files again, recompile, and then
>> it should work.  Right now the problem is that lld-link.exe hasn't been
>> compiled yet.
>>
>> On Fri, Jan 22, 2016 at 12:22 PM Red Skotina 
>> wrote:
>>
>>> yes, i miss it. but anyway dont work
>>>
>>>
>>> d:\code\Unity_Unpacker\tests\test2>clang -v -fuse-ld=lld main.cpp
>>> clang version 3.9.0 (trunk 258509)
>>> Target: i686-pc-windows-msvc
>>> Thread model: posix
>>> InstalledDir: d:\code\llvm\build\bin
>>>  "d:\\code\\llvm\\build\\bin\\clang.exe" -cc1 -triple
>>> i686-pc-windows-msvc18.0.0
>>>  -emit-obj -mrelax-all -mincremental-linker-compatible -disable-free
>>> -disable-ll
>>> vm-verifier -main-file-name main.cpp -mrelocation-model static
>>> -mthread-model po
>>> six -mdisable-fp-elim -fmath-errno -masm-verbose
>>> -mconstructor-aliases -target-c
>>> pu pentium4 -v -dwarf-column-info -debugger-tuning=gdb -resource-dir
>>> "d:\\code\\
>>> llvm\\build\\bin\\..\\lib\\clang\\3.9.0" -internal-isystem
>>> "d:\\code\\llvm\\buil
>>> d\\bin\\..\\lib\\clang\\3.9.0\\include" -internal-isystem
>>> "C:\\Program Files (x8
>>> 6)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE" -internal-isystem
>>> "C:\\Program Fi
>>> les (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\INCLUDE"
>>> -internal-isystem
>>> "C:\\Program Files (x86)\\Windows
>>> Kits\\10\\include\\10.0.10240.0\\ucrt" -intern
>>> al-isystem "C:\\Program Files (x86)\\Windows
>>> Kits\\NETFXSDK\\4.6.1\\include\\um"
>>>  -internal-isystem "C:\\Program Files (x86)\\Windows
>>> Kits\\8.1\\includeshare
>>> d" -internal-isystem "C:\\Program Files (x86)\\Windows
>>> Kits\\8.1\\includeum"
>>>  -internal-isystem "C:\\Program Files (x86)\\Windows
>>> Kits\\8.1\\includewinrt
>>> " -fdeprecated-macro -fdebug-compilation-dir
>>> "d:\\code\\Unity_Unpacker\\tests\\t
>>> est2" -ferror-limit 19 -fmessage-length 80 -fms-extensions
>>> -fms-compatibility -f
>>> ms-compatibility-version=18 -std=c++11 -fno-threadsafe-statics
>>> -fdelayed-templat
>>> e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option
>>> -fcolor-diagnostics -o "C
>>> :\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp
>>> clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target
>>> i686-pc-windows
>>> -msvc
>>> #include "..." search starts here:
>>> #include <...> search starts here:
>>>  d:\code\llvm\build\bin\..\lib\clang\3.9.0\include
>>>  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE
>>>  C:\Program Files (x86)\Microsoft Visual Studio
>>> 14.0\VC\ATLMFC\INCLUDE
>>>  C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt
>>>  C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um
>>>  C:\Program Files (x86)\Windows Kit

[lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

As of this week, we have the test suite running clean under MSVC 2015 using
Python 3.5.  I'm sure new things will pop up, but I'm considering the
transition "done" as of now.

What this means for MSVC 2013 is that we dont' want to support it anymore.

Reasons:
* C++ language support is poor
* Compiling your own version of Python is difficult and a high barrier to
entry for people wanting to build LLDB on Windows
* LLVM will eventually bump its minimum MSVC version to 2015 as well.

To this end, I have already changed the MSVC buildbot [
http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015] to compile
using 2015.  The old 2013 buildbot no longer exists.

This week I plan to update the build instructions on lldb.org to reflect
the simpler more streamlined instructions for 2015 and remove the
instructions for 2015.

I know some people are still using 2013.  I don't plan to break anything or
explicitly remove support from CMake or anywhere else for 2013.  I'm only
saying that unless someone else steps up to keep this configuration
working, it may break at any time, there won't be a buildbot testing it,
and I can't guarantee anything about it continuing to work.

Note that when LLVM bumps its minimum required version to MSVC 2015
(expected this year), it will be **very hard for anyone to continue using
Python 2 on Windows at tip of trunk**.  The only real workaround for this
is going to be forking Python (on your own end) and making whatever changes
are necessary to Python to keep it compiling, as they will not accept the
patches upstream.

Happy to answer any questions about this.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Tamas Berghammer via lldb-dev]

Hi Zachary,

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
Android Studio and we also have a buildbot what is testing this
configuration (without sending e-mail at the moment) here:
http://lab.llvm.org:8011/builders/lldb-windows7-android

We are in the discussion to decide what is our plan for going forward both
in terms of Visual Studio version and Python version and I expect that we
will make a decision this week. Until then please don't remove any hack we
have in the code because of MSVC 2013 (e.g. alias template workarounds) and
if adding new code then please try not to break MSVC 2013. I will send out
an update about our decision hopefully at the end of this week.

You mentioned that LLVM plan to bump the minimum version of MSVC to 2015.
Do you have any link to the place where they discussed it or do you know
anything about the schedule?

Thanks,
Tamas

On Tue, Feb 2, 2016 at 7:16 PM Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> As of this week, we have the test suite running clean under MSVC 2015
> using Python 3.5.  I'm sure new things will pop up, but I'm considering the
> transition "done" as of now.
>
> What this means for MSVC 2013 is that we dont' want to support it anymore.
>
> Reasons:
> * C++ language support is poor
> * Compiling your own version of Python is difficult and a high barrier to
> entry for people wanting to build LLDB on Windows
> * LLVM will eventually bump its minimum MSVC version to 2015 as well.
>
> To this end, I have already changed the MSVC buildbot [
> http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015] to compile
> using 2015.  The old 2013 buildbot no longer exists.
>
> This week I plan to update the build instructions on lldb.org to reflect
> the simpler more streamlined instructions for 2015 and remove the
> instructions for 2015.
>
> I know some people are still using 2013.  I don't plan to break anything
> or explicitly remove support from CMake or anywhere else for 2013.  I'm
> only saying that unless someone else steps up to keep this configuration
> working, it may break at any time, there won't be a buildbot testing it,
> and I can't guarantee anything about it continuing to work.
>
> Note that when LLVM bumps its minimum required version to MSVC 2015
> (expected this year), it will be **very hard for anyone to continue using
> Python 2 on Windows at tip of trunk**.  The only real workaround for this
> is going to be forking Python (on your own end) and making whatever changes
> are necessary to Python to keep it compiling, as they will not accept the
> patches upstream.
>
> Happy to answer any questions about this.
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer 
wrote:

> Hi Zachary,
>
> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
> Android Studio and we also have a buildbot what is testing this
> configuration (without sending e-mail at the moment) here:
> http://lab.llvm.org:8011/builders/lldb-windows7-android
>
> We are in the discussion to decide what is our plan for going forward both
> in terms of Visual Studio version and Python version and I expect that we
> will make a decision this week. Until then please don't remove any hack we
> have in the code because of MSVC 2013 (e.g. alias template workarounds) and
> if adding new code then please try not to break MSVC 2013. I will send out
> an update about our decision hopefully at the end of this week.
>
Yea I mentioned already that I'm not planning on removing anything related
to MSVC 2013, just that I'm personally not supporting it.  Which means that
if anyone asks for help, or wants to make it work, or if it breaks
accidentally, they're on their own :)  I don't even have MSVC 2013
installed on my machine anymore, so I can't fix any MSVC 2013 specific
issues that arise.

Of course if someone else comes along and wants to help, I have no problem
with that, but due to the difficulty of dealing with incompatibility
between Python 2 and MSVC 2015, it's just going to be up to someone else to
continue making that work if they need it.


>
> You mentioned that LLVM plan to bump the minimum version of MSVC to 2015.
> Do you have any link to the place where they discussed it or do you know
> anything about the schedule?
>

As far as I know the discussion hasn't started yet, but historically LLVM
has always been pretty consistent about bumping the required MSVC version
every 12-18 months.   I know some of the Windows people on the LLVM side
are already "unoficially" using MSVC 2015 on a regular basis, and that's
usually a sign that people are getting an early start to see what kind of
issues might be encountered by the general public when bumping the required
version.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Ted Woodward via lldb-dev]

It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , 
has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or 
VC. I’ll talk to our buildmiester about it.

 

Should we run this guy with 2013/py2.7 or 2015/py3.5?

 

--

Qualcomm Innovation Center, Inc.

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

 

From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Zachary 
Turner via lldb-dev
Sent: Tuesday, February 02, 2016 1:55 PM
To: Tamas Berghammer; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

 

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer mailto:tbergham...@google.com> > wrote:

Hi Zachary,

 

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for 
Android Studio and we also have a buildbot what is testing this configuration 
(without sending e-mail at the moment) here: 
http://lab.llvm.org:8011/builders/lldb-windows7-android

 

We are in the discussion to decide what is our plan for going forward both in 
terms of Visual Studio version and Python version and I expect that we will 
make a decision this week. Until then please don't remove any hack we have in 
the code because of MSVC 2013 (e.g. alias template workarounds) and if adding 
new code then please try not to break MSVC 2013. I will send out an update 
about our decision hopefully at the end of this week.

Yea I mentioned already that I'm not planning on removing anything related to 
MSVC 2013, just that I'm personally not supporting it.  Which means that if 
anyone asks for help, or wants to make it work, or if it breaks accidentally, 
they're on their own :)  I don't even have MSVC 2013 installed on my machine 
anymore, so I can't fix any MSVC 2013 specific issues that arise.

 

Of course if someone else comes along and wants to help, I have no problem with 
that, but due to the difficulty of dealing with incompatibility between Python 
2 and MSVC 2015, it's just going to be up to someone else to continue making 
that work if they need it.

 

 

You mentioned that LLVM plan to bump the minimum version of MSVC to 2015. Do 
you have any link to the place where they discussed it or do you know anything 
about the schedule?

 

As far as I know the discussion hasn't started yet, but historically LLVM has 
always been pretty consistent about bumping the required MSVC version every 
12-18 months.   I know some of the Windows people on the LLVM side are already 
"unoficially" using MSVC 2015 on a regular basis, and that's usually a sign 
that people are getting an early start to see what kind of issues might be 
encountered by the general public when bumping the required version.

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

If I remember correctly your bot isn't actually doing anything differently
than my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].
If you want you could just remove your bot.  If you want to keep it, then
yea getting it on VS2015 and Python 3 would be the best idea.

On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> It looks like our bot,
> http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , has tried to
> update to Python 3.5 and MSVC 2015, but it can’t find python or VC. I’ll
> talk to our buildmiester about it.
>
>
>
> Should we run this guy with 2013/py2.7 or 2015/py3.5?
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> *From:* lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] *On Behalf Of 
> *Zachary
> Turner via lldb-dev
> *Sent:* Tuesday, February 02, 2016 1:55 PM
> *To:* Tamas Berghammer; LLDB
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
>
>
> On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer 
> wrote:
>
> Hi Zachary,
>
>
>
> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
> Android Studio and we also have a buildbot what is testing this
> configuration (without sending e-mail at the moment) here:
> http://lab.llvm.org:8011/builders/lldb-windows7-android
>
>
>
> We are in the discussion to decide what is our plan for going forward both
> in terms of Visual Studio version and Python version and I expect that we
> will make a decision this week. Until then please don't remove any hack we
> have in the code because of MSVC 2013 (e.g. alias template workarounds) and
> if adding new code then please try not to break MSVC 2013. I will send out
> an update about our decision hopefully at the end of this week.
>
> Yea I mentioned already that I'm not planning on removing anything related
> to MSVC 2013, just that I'm personally not supporting it.  Which means that
> if anyone asks for help, or wants to make it work, or if it breaks
> accidentally, they're on their own :)  I don't even have MSVC 2013
> installed on my machine anymore, so I can't fix any MSVC 2013 specific
> issues that arise.
>
>
>
> Of course if someone else comes along and wants to help, I have no problem
> with that, but due to the difficulty of dealing with incompatibility
> between Python 2 and MSVC 2015, it's just going to be up to someone else to
> continue making that work if they need it.
>
>
>
>
>
> You mentioned that LLVM plan to bump the minimum version of MSVC to 2015.
> Do you have any link to the place where they discussed it or do you know
> anything about the schedule?
>
>
>
> As far as I know the discussion hasn't started yet, but historically LLVM
> has always been pretty consistent about bumping the required MSVC version
> every 12-18 months.   I know some of the Windows people on the LLVM side
> are already "unoficially" using MSVC 2015 on a regular basis, and that's
> usually a sign that people are getting an early start to see what kind of
> issues might be encountered by the general public when bumping the required
> version.
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [3.8 Release] RC2 has been tagged

[Hans Wennborg via lldb-dev]

Dear testers,

Release Candidate 2 has just been tagged [1]. Please build, test, and
upload to the sftp.

I know there are still outstanding issues from RC1, but there have
been a lot of merges going into the branch and I think it's time for
another round of RC testing.

This RC comes a little behind schedule, sorry about that, but I'm
still optimistic about hitting the target of releasing towards the end
of February.

Thanks for all the work you've put into this release so far!

Hans

 [1] 
http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009739.html
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Ted Woodward via lldb-dev]

Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.

 

--

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:ztur...@google.com] 
Sent: Tuesday, February 02, 2016 2:48 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

If I remember correctly your bot isn't actually doing anything differently than 
my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].  If you 
want you could just remove your bot.  If you want to keep it, then yea getting 
it on VS2015 and Python 3 would be the best idea.

 

On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev 
mailto:lldb-dev@lists.llvm.org> > wrote:

It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , 
has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or 
VC. I’ll talk to our buildmiester about it.

 

Should we run this guy with 2013/py2.7 or 2015/py3.5?

 

--

Qualcomm Innovation Center, Inc.

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

 

From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org 
 ] On Behalf Of Zachary Turner via 
lldb-dev
Sent: Tuesday, February 02, 2016 1:55 PM
To: Tamas Berghammer; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

 

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer mailto:tbergham...@google.com> > wrote:

Hi Zachary,

 

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for 
Android Studio and we also have a buildbot what is testing this configuration 
(without sending e-mail at the moment) here: 
http://lab.llvm.org:8011/builders/lldb-windows7-android

 

We are in the discussion to decide what is our plan for going forward both in 
terms of Visual Studio version and Python version and I expect that we will 
make a decision this week. Until then please don't remove any hack we have in 
the code because of MSVC 2013 (e.g. alias template workarounds) and if adding 
new code then please try not to break MSVC 2013. I will send out an update 
about our decision hopefully at the end of this week.

Yea I mentioned already that I'm not planning on removing anything related to 
MSVC 2013, just that I'm personally not supporting it.  Which means that if 
anyone asks for help, or wants to make it work, or if it breaks accidentally, 
they're on their own :)  I don't even have MSVC 2013 installed on my machine 
anymore, so I can't fix any MSVC 2013 specific issues that arise.

 

Of course if someone else comes along and wants to help, I have no problem with 
that, but due to the difficulty of dealing with incompatibility between Python 
2 and MSVC 2015, it's just going to be up to someone else to continue making 
that work if they need it.

 

 

You mentioned that LLVM plan to bump the minimum version of MSVC to 2015. Do 
you have any link to the place where they discussed it or do you know anything 
about the schedule?

 

As far as I know the discussion hasn't started yet, but historically LLVM has 
always been pretty consistent about bumping the required MSVC version every 
12-18 months.   I know some of the Windows people on the LLVM side are already 
"unoficially" using MSVC 2015 on a regular basis, and that's usually a sign 
that people are getting an early start to see what kind of issues might be 
encountered by the general public when bumping the required version.

___
lldb-dev mailing list
lldb-dev@lists.llvm.org  
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

It's Server 2008 R2 technically, which is the server version of Win 7 (same
API set, same OS features, etc).  So yea, I'm pretty confident that test
coverage is going to be 100% the same across both.  It's just a matter of
if you want to have something that you maintain / have control over, or if
you want to test something in a different way than what we're testing.

On Tue, Feb 2, 2016 at 1:29 PM Ted Woodward 
wrote:

> Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.
>
>
>
> --
>
> 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:ztur...@google.com]
> *Sent:* Tuesday, February 02, 2016 2:48 PM
> *To:* Ted Woodward; LLDB
>
>
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
> If I remember correctly your bot isn't actually doing anything differently
> than my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].
> If you want you could just remove your bot.  If you want to keep it, then
> yea getting it on VS2015 and Python 3 would be the best idea.
>
>
>
> On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> It looks like our bot,
> http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , has tried to
> update to Python 3.5 and MSVC 2015, but it can’t find python or VC. I’ll
> talk to our buildmiester about it.
>
>
>
> Should we run this guy with 2013/py2.7 or 2015/py3.5?
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> *From:* lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] *On Behalf Of 
> *Zachary
> Turner via lldb-dev
> *Sent:* Tuesday, February 02, 2016 1:55 PM
> *To:* Tamas Berghammer; LLDB
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
>
>
> On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer 
> wrote:
>
> Hi Zachary,
>
>
>
> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
> Android Studio and we also have a buildbot what is testing this
> configuration (without sending e-mail at the moment) here:
> http://lab.llvm.org:8011/builders/lldb-windows7-android
>
>
>
> We are in the discussion to decide what is our plan for going forward both
> in terms of Visual Studio version and Python version and I expect that we
> will make a decision this week. Until then please don't remove any hack we
> have in the code because of MSVC 2013 (e.g. alias template workarounds) and
> if adding new code then please try not to break MSVC 2013. I will send out
> an update about our decision hopefully at the end of this week.
>
> Yea I mentioned already that I'm not planning on removing anything related
> to MSVC 2013, just that I'm personally not supporting it.  Which means that
> if anyone asks for help, or wants to make it work, or if it breaks
> accidentally, they're on their own :)  I don't even have MSVC 2013
> installed on my machine anymore, so I can't fix any MSVC 2013 specific
> issues that arise.
>
>
>
> Of course if someone else comes along and wants to help, I have no problem
> with that, but due to the difficulty of dealing with incompatibility
> between Python 2 and MSVC 2015, it's just going to be up to someone else to
> continue making that work if they need it.
>
>
>
>
>
> You mentioned that LLVM plan to bump the minimum version of MSVC to 2015.
> Do you have any link to the place where they discussed it or do you know
> anything about the schedule?
>
>
>
> As far as I know the discussion hasn't started yet, but historically LLVM
> has always been pretty consistent about bumping the required MSVC version
> every 12-18 months.   I know some of the Windows people on the LLVM side
> are already "unoficially" using MSVC 2015 on a regular basis, and that's
> usually a sign that people are getting an early start to see what kind of
> issues might be encountered by the general public when bumping the required
> version.
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Ted Woodward via lldb-dev]

Then maybe we should keep it 2013/py2.7, until llvm requires 2015.

 

--

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:ztur...@google.com] 
Sent: Tuesday, February 02, 2016 3:43 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

It's Server 2008 R2 technically, which is the server version of Win 7 (same API 
set, same OS features, etc).  So yea, I'm pretty confident that test coverage 
is going to be 100% the same across both.  It's just a matter of if you want to 
have something that you maintain / have control over, or if you want to test 
something in a different way than what we're testing.

 

On Tue, Feb 2, 2016 at 1:29 PM Ted Woodward mailto:ted.woodw...@codeaurora.org> > wrote:

Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.

 

--

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:ztur...@google.com  ] 
Sent: Tuesday, February 02, 2016 2:48 PM
To: Ted Woodward; LLDB


Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

If I remember correctly your bot isn't actually doing anything differently than 
my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].  If you 
want you could just remove your bot.  If you want to keep it, then yea getting 
it on VS2015 and Python 3 would be the best idea.

 

On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev 
mailto:lldb-dev@lists.llvm.org> > wrote:

It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , 
has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or 
VC. I’ll talk to our buildmiester about it.

 

Should we run this guy with 2013/py2.7 or 2015/py3.5?

 

--

Qualcomm Innovation Center, Inc.

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

 

From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org 
 ] On Behalf Of Zachary Turner via 
lldb-dev
Sent: Tuesday, February 02, 2016 1:55 PM
To: Tamas Berghammer; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

 

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer mailto:tbergham...@google.com> > wrote:

Hi Zachary,

 

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for 
Android Studio and we also have a buildbot what is testing this configuration 
(without sending e-mail at the moment) here: 
http://lab.llvm.org:8011/builders/lldb-windows7-android

 

We are in the discussion to decide what is our plan for going forward both in 
terms of Visual Studio version and Python version and I expect that we will 
make a decision this week. Until then please don't remove any hack we have in 
the code because of MSVC 2013 (e.g. alias template workarounds) and if adding 
new code then please try not to break MSVC 2013. I will send out an update 
about our decision hopefully at the end of this week.

Yea I mentioned already that I'm not planning on removing anything related to 
MSVC 2013, just that I'm personally not supporting it.  Which means that if 
anyone asks for help, or wants to make it work, or if it breaks accidentally, 
they're on their own :)  I don't even have MSVC 2013 installed on my machine 
anymore, so I can't fix any MSVC 2013 specific issues that arise.

 

Of course if someone else comes along and wants to help, I have no problem with 
that, but due to the difficulty of dealing with incompatibility between Python 
2 and MSVC 2015, it's just going to be up to someone else to continue making 
that work if they need it.

 

 

You mentioned that LLVM plan to bump the minimum version of MSVC to 2015. Do 
you have any link to the place where they discussed it or do you know anything 
about the schedule?

 

As far as I know the discussion hasn't started yet, but historically LLVM has 
always been pretty consistent about bumping the required MSVC version every 
12-18 months.   I know some of the Windows people on the LLVM side are already 
"unoficially" using MSVC 2015 on a regular basis, and that's usually a sign 
that people are getting an early start to see what kind of issues might be 
encountered by the general public when bumping the required version.

___
lldb-dev mailing list
lldb-dev@lists.llvm.org  
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

You may have to make some changes to the zorg scripts to keep that
working.  I didn't realize there were any other bots building LLDB, so I
made some changes that will default everything to VS2015 and Py3.

BTW, is your builder doing a debug build or a release build?  When doing a
debug build clang now requires more memory than can fit in a 4GB address
space to link, so using an x86 toolchain won't work anymore.  I forced a
change to use the amd64_x86 toolchain, but this won't work unless the
version of python used by buildbot is a 64-bit Python distro (because
Python.exe is what ultimately calls vcvarsall and cmake and it inherits the
environment of the parent).

So I think you will need to do all this as well.

On Tue, Feb 2, 2016 at 1:44 PM Ted Woodward 
wrote:

> Then maybe we should keep it 2013/py2.7, until llvm requires 2015.
>
>
>
> --
>
> 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:ztur...@google.com]
> *Sent:* Tuesday, February 02, 2016 3:43 PM
>
>
> *To:* Ted Woodward; LLDB
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
> It's Server 2008 R2 technically, which is the server version of Win 7
> (same API set, same OS features, etc).  So yea, I'm pretty confident that
> test coverage is going to be 100% the same across both.  It's just a matter
> of if you want to have something that you maintain / have control over, or
> if you want to test something in a different way than what we're testing.
>
>
>
> On Tue, Feb 2, 2016 at 1:29 PM Ted Woodward 
> wrote:
>
> Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.
>
>
>
> --
>
> 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:ztur...@google.com]
> *Sent:* Tuesday, February 02, 2016 2:48 PM
> *To:* Ted Woodward; LLDB
>
>
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
> If I remember correctly your bot isn't actually doing anything differently
> than my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].
> If you want you could just remove your bot.  If you want to keep it, then
> yea getting it on VS2015 and Python 3 would be the best idea.
>
>
>
> On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> It looks like our bot,
> http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , has tried to
> update to Python 3.5 and MSVC 2015, but it can’t find python or VC. I’ll
> talk to our buildmiester about it.
>
>
>
> Should we run this guy with 2013/py2.7 or 2015/py3.5?
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> *From:* lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] *On Behalf Of 
> *Zachary
> Turner via lldb-dev
> *Sent:* Tuesday, February 02, 2016 1:55 PM
> *To:* Tamas Berghammer; LLDB
> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
>
>
>
>
>
> On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer 
> wrote:
>
> Hi Zachary,
>
>
>
> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
> Android Studio and we also have a buildbot what is testing this
> configuration (without sending e-mail at the moment) here:
> http://lab.llvm.org:8011/builders/lldb-windows7-android
>
>
>
> We are in the discussion to decide what is our plan for going forward both
> in terms of Visual Studio version and Python version and I expect that we
> will make a decision this week. Until then please don't remove any hack we
> have in the code because of MSVC 2013 (e.g. alias template workarounds) and
> if adding new code then please try not to break MSVC 2013. I will send out
> an update about our decision hopefully at the end of this week.
>
> Yea I mentioned already that I'm not planning on removing anything related
> to MSVC 2013, just that I'm personally not supporting it.  Which means that
> if anyone asks for help, or wants to make it work, or if it breaks
> accidentally, they're on their own :)  I don't even have MSVC 2013
> installed on my machine anymore, so I can't fix any MSVC 2013 specific
> issues that arise.
>
>
>
> Of course if someone else comes along and wants to help, I have no problem
> with that, but due to the difficulty of dealing with incompatibility
> between Python 2 and MSVC 2015, it's just going to be up to someone else to
> continue making that work if they need it.
>
>
>
>
>
> You mentioned that LLVM plan to bump the minimum version of MSVC to 2015.
> Do you have any link to the place where they discussed it or do you know
> anything about the schedule?
>
>
>
> As far as I know the discussion hasn't started 

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Zachary Turner via lldb-dev]

BTW, I expect that your buildbot has been experiencing the problems with
the x86 / x64 toolchain for quite some time, because it's not really
relevant to how much memory your machine has, but just that it was using an
x86 toolchain at all.  Has it been red for a long time?

On Tue, Feb 2, 2016 at 1:48 PM Zachary Turner  wrote:

> You may have to make some changes to the zorg scripts to keep that
> working.  I didn't realize there were any other bots building LLDB, so I
> made some changes that will default everything to VS2015 and Py3.
>
> BTW, is your builder doing a debug build or a release build?  When doing a
> debug build clang now requires more memory than can fit in a 4GB address
> space to link, so using an x86 toolchain won't work anymore.  I forced a
> change to use the amd64_x86 toolchain, but this won't work unless the
> version of python used by buildbot is a 64-bit Python distro (because
> Python.exe is what ultimately calls vcvarsall and cmake and it inherits the
> environment of the parent).
>
> So I think you will need to do all this as well.
>
> On Tue, Feb 2, 2016 at 1:44 PM Ted Woodward 
> wrote:
>
>> Then maybe we should keep it 2013/py2.7, until llvm requires 2015.
>>
>>
>>
>> --
>>
>> 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:ztur...@google.com]
>> *Sent:* Tuesday, February 02, 2016 3:43 PM
>>
>>
>> *To:* Ted Woodward; LLDB
>> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
>> unsupported toolchain
>>
>>
>>
>> It's Server 2008 R2 technically, which is the server version of Win 7
>> (same API set, same OS features, etc).  So yea, I'm pretty confident that
>> test coverage is going to be 100% the same across both.  It's just a matter
>> of if you want to have something that you maintain / have control over, or
>> if you want to test something in a different way than what we're testing.
>>
>>
>>
>> On Tue, Feb 2, 2016 at 1:29 PM Ted Woodward 
>> wrote:
>>
>> Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.
>>
>>
>>
>> --
>>
>> 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:ztur...@google.com]
>> *Sent:* Tuesday, February 02, 2016 2:48 PM
>> *To:* Ted Woodward; LLDB
>>
>>
>> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
>> unsupported toolchain
>>
>>
>>
>> If I remember correctly your bot isn't actually doing anything
>> differently than my bot [
>> http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].  If you
>> want you could just remove your bot.  If you want to keep it, then yea
>> getting it on VS2015 and Python 3 would be the best idea.
>>
>>
>>
>> On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> It looks like our bot,
>> http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , has tried to
>> update to Python 3.5 and MSVC 2015, but it can’t find python or VC. I’ll
>> talk to our buildmiester about it.
>>
>>
>>
>> Should we run this guy with 2013/py2.7 or 2015/py3.5?
>>
>>
>>
>> --
>>
>> Qualcomm Innovation Center, Inc.
>>
>> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
>> Linux Foundation Collaborative Project
>>
>>
>>
>> *From:* lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] *On Behalf Of 
>> *Zachary
>> Turner via lldb-dev
>> *Sent:* Tuesday, February 02, 2016 1:55 PM
>> *To:* Tamas Berghammer; LLDB
>> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
>> unsupported toolchain
>>
>>
>>
>>
>>
>> On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer 
>> wrote:
>>
>> Hi Zachary,
>>
>>
>>
>> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows
>> for Android Studio and we also have a buildbot what is testing this
>> configuration (without sending e-mail at the moment) here:
>> http://lab.llvm.org:8011/builders/lldb-windows7-android
>>
>>
>>
>> We are in the discussion to decide what is our plan for going forward
>> both in terms of Visual Studio version and Python version and I expect that
>> we will make a decision this week. Until then please don't remove any hack
>> we have in the code because of MSVC 2013 (e.g. alias template workarounds)
>> and if adding new code then please try not to break MSVC 2013. I will send
>> out an update about our decision hopefully at the end of this week.
>>
>> Yea I mentioned already that I'm not planning on removing anything
>> related to MSVC 2013, just that I'm personally not supporting it.  Which
>> means that if anyone asks for help, or wants to make it work, or if it
>> breaks accidentally, they're on their own :)  I don't even have MSVC 2013
>> installed on my machine anymore, so I can't fix any MSVC 2013 specific
>> issues that arise.
>>
>>
>>
>> Of course if someone 

Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Ted Woodward via lldb-dev]

No, it turned red Friday night/Saturday morning.

 

Last good build:

http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/15167

 

First bad build:

http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/15168

 

It went red because of the change to VS2015/Python 3.5.

 

--

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:ztur...@google.com] 
Sent: Tuesday, February 02, 2016 5:28 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

BTW, I expect that your buildbot has been experiencing the problems with the 
x86 / x64 toolchain for quite some time, because it's not really relevant to 
how much memory your machine has, but just that it was using an x86 toolchain 
at all.  Has it been red for a long time?

 

On Tue, Feb 2, 2016 at 1:48 PM Zachary Turner mailto:ztur...@google.com> > wrote:

You may have to make some changes to the zorg scripts to keep that working.  I 
didn't realize there were any other bots building LLDB, so I made some changes 
that will default everything to VS2015 and Py3.  

 

BTW, is your builder doing a debug build or a release build?  When doing a 
debug build clang now requires more memory than can fit in a 4GB address space 
to link, so using an x86 toolchain won't work anymore.  I forced a change to 
use the amd64_x86 toolchain, but this won't work unless the version of python 
used by buildbot is a 64-bit Python distro (because Python.exe is what 
ultimately calls vcvarsall and cmake and it inherits the environment of the 
parent).

 

So I think you will need to do all this as well.

 

On Tue, Feb 2, 2016 at 1:44 PM Ted Woodward mailto:ted.woodw...@codeaurora.org> > wrote:

Then maybe we should keep it 2013/py2.7, until llvm requires 2015.

 

--

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:ztur...@google.com  ] 
Sent: Tuesday, February 02, 2016 3:43 PM


To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

It's Server 2008 R2 technically, which is the server version of Win 7 (same API 
set, same OS features, etc).  So yea, I'm pretty confident that test coverage 
is going to be 100% the same across both.  It's just a matter of if you want to 
have something that you maintain / have control over, or if you want to test 
something in a different way than what we're testing.

 

On Tue, Feb 2, 2016 at 1:29 PM Ted Woodward mailto:ted.woodw...@codeaurora.org> > wrote:

Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.

 

--

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:ztur...@google.com  ] 
Sent: Tuesday, February 02, 2016 2:48 PM
To: Ted Woodward; LLDB


Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

If I remember correctly your bot isn't actually doing anything differently than 
my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].  If you 
want you could just remove your bot.  If you want to keep it, then yea getting 
it on VS2015 and Python 3 would be the best idea.

 

On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev 
mailto:lldb-dev@lists.llvm.org> > wrote:

It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , 
has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or 
VC. I’ll talk to our buildmiester about it.

 

Should we run this guy with 2013/py2.7 or 2015/py3.5?

 

--

Qualcomm Innovation Center, Inc.

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

 

From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org 
 ] On Behalf Of Zachary Turner via 
lldb-dev
Sent: Tuesday, February 02, 2016 1:55 PM
To: Tamas Berghammer; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported 
toolchain

 

 

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer mailto:tbergham...@google.com> > wrote:

Hi Zachary,

 

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for 
Android Studio and we also have a buildbot what is testing this configuration 
(without sending e-mail at the moment) here: 
http://lab.llvm.org:8011/builders/lldb-windows7-android

 

We are in the discussion to decide what is our plan for going forward both in 
terms of Visual Studio version and Python version and I expect that we will 
make a decision this week. Until then please don't remove any hack we have in 
the code because of MSVC 2013 (e.g. alias