>>> Last time I tried, it wasn't "reasonable" enough to start debugging
>> a
>>> program under Emacs. See this discussion for details:
>>>
>>> http://lists.llvm.org/pipermail/llvm-dev/2016-December/108512.html
>>>
>>> The failed commands it shows are the initial ones issued by Emacs
>>> when a
https://bugs.llvm.org/show_bug.cgi?id=32362
Vedran Miletic changed:
What|Removed |Added
Status|NEW |RESOLVED
On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric wrote:
> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev
> wrote:
>>
>> 5.0.0-rc1 has just been tagged.
>>
>> Please build, test and upload binaries to the sftp. Let me know if
>> there are any
On 31 Jul 2017, at 19:26, Hans Wennborg wrote:
>
> On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric wrote:
>> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev
>> wrote:
>>>
>>> 5.0.0-rc1 has just been tagged.
>>>
>>> Please
> From: "Ted Woodward"
> Cc:
> Date: Mon, 31 Jul 2017 13:24:31 -0500
>
> The best thing to do is give us a list of commands that are failing, in a bug
> opened in Bugzilla at http://bugs.llvm.org .
The URL I provided (after several mistaken
The original lldb-mi implementation was to get Eclipse talking to lldb. Since
then there have been other people working on it, and other clients, but lldb-mi
is not a full implementation of the MI protocol.
The best thing to do is give us a list of commands that are failing, in a bug
opened in
> On Jul 24, 2017, at 10:48 AM, Sean Callanan via lldb-dev
> wrote:
>
> Steve,
>
> since you asked about failures, here are some public bots you can look at to
> get a general sense of how we are doing:
>
> http://lab.llvm.org:8011/builders
We'll be at Tied House as usual, starting on Thursday the 3rd at 7pm!
If you can, help us plan and RSVP here: http://meetu.ps/3bRM2c
See everyone there!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
Hello all,
Source, binaries and docs for LLVM-5.0.0-rc1 are now available at
http://prereleases.llvm.org/5.0.0/#rc1
Please try it out, run tests, builds your favourite projects and file
bugs about anything that needs to be fixed (including docs!), marking
them blockers of