Re: [lldb-dev] [4.0.0 Release] 'final' has been tagged

2017-03-10 Thread Hans Wennborg via lldb-dev 
On Thu, Mar 9, 2017 at 2:28 PM, Hans Wennborg  wrote:
> On Wed, Mar 8, 2017 at 4:52 PM, Hans Wennborg  wrote:
>> Dear testers,
>>
>> The final version of 4.0.0 was just tagged (from the 4.0 branch at
>> r297335). There were no changes after rc4.
>>
>> Please build the final binaries and upload to the sftp.
>
> Windows:
>
> $ sha1sum *LLVM-4.0.0-win*.exe
> b48a3dab37e2a1b5a5446b316832b9b80c6bd557  LLVM-4.0.0-win32.exe
> 5588c00484d5e1fe05bcce8201282b172448f6fc  LLVM-4.0.0-win64.exe
>
> Build script attached.

I was asked about Ubuntu x86_64 Ubuntu 14.04, so I built a package for that too:

$ sha256sum *.xz
1d15b6337ffc0876ed1a9827cae566e24639e0f5d7d186b2de04c38d762336b4
clang+llvm-4.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [4.0.0 Release] 'final' has been tagged

2017-03-10 Thread Renato Golin via lldb-dev 
ARM and AArch64 looking good, uploaded.

4e62f3d5dcc95189eaec2d950950876a423f8a8c
clang+llvm-4.0.0-aarch64-linux-gnu.tar.xz
1b031f16683e3bcd779f50e6d47d0d1f3f265e9f
clang+llvm-4.0.0-armv7a-linux-gnueabihf.tar.xz

On 10 March 2017 at 12:14, Ben Pope via cfe-dev  wrote:
> On 09/03/17 00:52, Hans Wennborg via cfe-dev wrote:
>>
>> Dear testers,
>>
>> The final version of 4.0.0 was just tagged (from the 4.0 branch at
>> r297335). There were no changes after rc4.
>>
>> Please build the final binaries and upload to the sftp.
>
>
> All done for Ubuntu x64:
>
> clang+llvm-4.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz
> clang+llvm-4.0.0-x86_64-linux-gnu-ubuntu-16.10.tar.xz
>
> Ben
>
>
>
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] exitting from batch processing

2017-03-10 Thread René J . V . Bertin via lldb-dev 
Hi,

I'm working on a crash reporter tool that invokes and controls lldb through a 
batchfile. As described 
(http://stackoverflow.com/questions/26267289/how-can-i-exit-lldb-after-running-commands-with-o)
 it is tricky to get older lldb versions to exit cleanly because they don't 
react as they should to the quit command. Sadly this concerns the "system" lldb 
version shipped with Apple's dev. tools for at least OS X 10.9 .

The stackoverflow page describes a hack using a python script, which works, but 
which evidently requires a python interpreter to be integrated with lldb.

Supposing it is still possible to build lldb without python, what happens when 
it is called this way?

%> lldb -p  -o bt -o continue -o detach -o "script import os ; 
os._exit(0)" -o quit

Errors in the python script (e.g. import os2) don't interrupt the batch 
processing and lldb will quit because of the subsequent "quit" command. But 
what if python isn't available?

Thanks,

R.

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

[lldb-dev] Unsupported instruction call

2017-03-10 Thread Carlo Kok via lldb-dev 

Trying to evaluate:

((unsigned short* (*)(void *))10544800)((void*)44769264)

or

((unsigned short* (*)(void *))_ElementsGetTypeName)((void*)44769264)

in lldb/windows gives me
Unsupported instruction: %call = call i16* inttoptr (i32 16967328 to 
i16* (i8*)*)(i8* inttoptr (i32 15867888 to i8*))



Seems to be triggered by support_function_calls being false(but I can't 
see who would ever set this to true)


what am I missing?
--
Carlo Kok
RemObjects Software
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev