Re: [lldb-dev] [9.0.0 Release] Release Candidate 6 is here

2019-09-19 Thread Diana Picus via lldb-dev
Hi,

Same as before.

b70d9b0f83ea0df0d59f54445930110f9d7819afd46dd1824853d9cf92ff2164
clang+llvm-9.0.0-rc6-armv7a-linux-gnueabihf.tar.xz
6be0e426f2ecaefb38813321d467746eb67b1f736024dde46eb1500b49d4af91
clang+llvm-9.0.0-rc6-aarch64-linux-gnu.tar.xz

Cheers,
Diana


On Tue, 17 Sep 2019 at 16:05, Hans Wennborg via lldb-dev
 wrote:
>
> Hello everyone,
>
> 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In
> the Git monorepo, it's tagged as llvmorg-9.0.0-rc6.
>
> Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc6
>
> This is the same as rc5 plus one very minor change (r371969) that
> still seemed good to pick up.
>
> I'm not allocating extra time for testing this one, expecting to tag
> 'final' in a day or two unless any new problem arises. If you still
> have cycles to spare, testing is still very much appreciated of
> course.
>
> As usual, please file bug reports about any issues you find, marking
> them blocking of https://llvm.org/PR42474
>
> Thanks,
> Hans
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [9.0.0 Release] Release Candidate 6 is here

2019-09-19 Thread Hans Wennborg via lldb-dev
On Tue, Sep 17, 2019 at 4:05 PM Hans Wennborg  wrote:
>
> Hello everyone,
>
> 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In
> the Git monorepo, it's tagged as llvmorg-9.0.0-rc6.

This has now been tagged as the final 9.0.0 release. In the Git
monorepo, it's tagged as llvmorg-9.0.0.

The official release announcement will follow as soon as the source
tarballs and docs are ready on the web page.

Testers: please start building the final binaries, and I'll add them
as they become ready.

Many thanks for your hard work!
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Stepping in a breakpoint callback with Python

2019-09-19 Thread Jim Ingham via lldb-dev
lldb doesn’t currently support breakpoint callbacks that try to control running 
the target in the callback.  I’m not sure how easy it would be to support that 
reliably, but anyway, that doesn’t work at present.

My model for this sort of tracing activity is that you are writing a fancy kind 
of “step” operation.  You would write a fancy step & record plan that would 
proceed along however you wanted and log at each stop.  Then your breakpoint 
callback would just queue up this step-and-trace plan as its last act.  That’s 
what the Scripted ThreadPlans are for:

https://lldb.llvm.org/use/python-reference.html#using-the-python-api-to-create-custom-stepping-logic

I’m not quite sure what you are describing with the process events approach.  
Are you trying to do this while also running in the lldb driver, or can you 
write a stand-alone tool to do this?  If the latter, then it should be enough 
to program everything at the event loop level.  You will know when your 
breakpoint is hit, then you can issue the steps one by one and do whatever 
logging you want each time you stop.  I’m not sure why this would need events 
sent from the breakpoint callback.

Jim

> On Sep 18, 2019, at 7:59 PM, Nikita Karetnikov via lldb-dev 
>  wrote:
> 
> Hello,
> 
> I'm trying to figure out how to write a simple tracer.  Specifically, I want 
> to
> perform some 'step's after a breakpoint callback fires.  How do I do that in
> async mode?
> 
> Here's my attempt:
> https://gist.github.com/nkaretnikov/6ee00afabf73332c5a89eacb610369c2 
> 
> 
> The problem is that pc is not updated (pc: 0x) when the loop
> executes the second time.
> 
> I've also attempted to refactor this code based on:
> http://llvm.org/svn/llvm-project/lldb/trunk/examples/python/process_events.py 
> 
> 
> My idea was to have a similar loop as the one that's after 'listener = ...'.  
> It
> would sit there waiting for events, and I would somehow broadcast an event 
> from
> the callback.  Maybe with 'state == lldb.eStateStopped' and a global variable
> allowing me to distinguish this event type from the rest.
> 
> But I can't find a way to do this.  Either I get the same behavior as without
> events or my events are ignored completely (likely because I use them
> incorrectly).
> 
> I haven't published the code of the event version, but I can do that later
> unless someone proposes a working solution right away.
> 
> Thanks,
> Nikita
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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


[lldb-dev] LLVM 9.0.0 Release

2019-09-19 Thread Hans Wennborg via lldb-dev
It's my great pleasure to announce that LLVM 9 is now available.

Get it here: https://llvm.org/releases/download.html#9.0.0

This release is the result of the LLVM community's work over the past
six months (up to trunk r366426 plus commits on the branch). Some
highlights include:

- Support for asm goto, enabling for example the mainline Linux kernel
  for x86_64 to build with Clang
- The RISCV-V target is no longer experimental, but built by default
- Experimental support for C++ for OpenCL

as well as many bug fixes, optimizations, and diagnostics improvements.

For more details, see the release notes:
https://llvm.org/releases/9.0.0/docs/ReleaseNotes.html
https://llvm.org/releases/9.0.0/tools/clang/docs/ReleaseNotes.html
https://llvm.org/releases/9.0.0/tools/clang/tools/extra/docs/ReleaseNotes.html
https://llvm.org/releases/9.0.0/tools/lld/docs/ReleaseNotes.html
https://llvm.org/releases/9.0.0/projects/libcxx/docs/ReleaseNotes.html

Special thanks to the release testers and packagers: Amy Kwan, Andrew
Kelley, Bernhard Rosenkraenzer, Brian Cain, Diana Picus, Dimitry
Andric, Jonas Hahnfeld, Khem Raj, Michał Górny, Neil Nelson, Nick
Desaulniers, Sylvestre Ledru, and Victor Huang. Without your work,
this would not be possible.

For questions or comments about the release, please contact the
community on the mailing lists. Onwards to LLVM 10!

Thanks,
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev