I’ve pondered integrating the REPL into LLDB - but what I really want/need is
for all of this to run within SLIME - and I don’t know enough about it to do
that.
I do know how to talk to complex C++ API’s from Common Lisp - hence my line of
questioning.
I’ll think on that more though. What you
On Tue, 29 Aug 2017 21:05:32 +0200, meister via lldb-dev wrote:
> Common Lisp is a different kind of language - it’s never supposed to seg
> fault. :-)
>
> It’s a dynamic language that I am compiling to llvm-ir and using to call and
> drive C++ libraries.
> The integrated debugger takes over when
Common Lisp is a different kind of language - it’s never supposed to seg fault.
:-)
It’s a dynamic language that I am compiling to llvm-ir and using to call and
drive C++ libraries.
The integrated debugger takes over when an error is signaled and it should
allow the user to view the stack, insp
By the way: "swift" ends up executing:
/Applications/Xcode.app/Contents/Developer/usr/bin/lldb
--repl=-enable-objc-interop -sdk
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk
-color-diagnostics
> On Aug 29, 2017, at 12:03 PM, Greg Clayton
> On Aug 29, 2017, at 11:41 AM, meister wrote:
>
> Greg,
>
> We are developing a compiler for Common Lisp that uses LLVM as the backend
> and interoperates with C++ - it has its own REPL and built in compiler.
> Our compiler generates llvm-ir that we link directly with llvm-ir generated
>
Project
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of meister
via lldb-dev
Sent: Tuesday, August 29, 2017 1:41 PM
To: clayb...@gmail.com
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Linking the lldb C++API/library with other projects
Greg,
We are developing a
On Tue, 29 Aug 2017 20:17:57 +0200, meister via lldb-dev wrote:
> (i) My program detects an error and enters into its debugger.
> (ii) It forks a debugging process and that interacts with the user who uses
> it to debug the main process.
> (iii) The debugger process shuts down and the main process
Greg,
We are developing a compiler for Common Lisp that uses LLVM as the backend and
interoperates with C++ - it has its own REPL and built in compiler.
Our compiler generates llvm-ir that we link directly with llvm-ir generated
from the C++ code using LTO.
I’ve exposed much of the LLVM C++ A
> On Aug 29, 2017, at 11:17 AM, meister wrote:
>
> Dear Greg,
>
> Thank you very much for your detailed and thoughtful response.
>
> A couple of followup questions based on what you said:
>
> (1) You say: "since LLDB can't be used to backtrace itself…"
> Do I (a) need to fork another process
Dear Greg,
Thank you very much for your detailed and thoughtful response.
A couple of followup questions based on what you said:
(1) You say: "since LLDB can't be used to backtrace itself…"
Do I (a) need to fork another process and call the LLDB API’s to get backtraces
for the original process
> On Aug 29, 2017, at 8:21 AM, meister via lldb-dev
> wrote:
>
> Does anyone have pointers on how to link the lldb C++ API/library with
> another project that uses a command line driven build system?
You can always use "xcodebuild" if you need to for Mac builds:
lldb:
cd /tmp/lldb
xc
11 matches
Mail list logo
