lldb-mi
clasp
lldb-mi | clasp | |
---|---|---|
11 | 47 | |
150 | 2,508 | |
1.3% | 0.6% | |
4.6 | 9.7 | |
2 months ago | 6 days ago | |
C++ | Common Lisp | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lldb-mi
-
My Personal Serverless Rust Developer Experience. It’s Better Than You Think
I'm on the record of loving the VSCode experience with Rust. And I do think that it's amazing that a "non-IDE" can feel so much like an IDE. However, I've recently pivoted off of that stance. I know it's still in EAP, but Rust Rover gives me all of the things that I get from VSCode plus an easier integration with LLDB.
-
Taming the dragon: using llnode to debug your Node.js application
Fortunately, we can use this same technique with our Node.js applications! This is possible through llnode: a LLDB plugin which enables us to inspect Node.js core dumps. With llnode, we can inspect objects in the memory and look at the complete backtrace of the program, including native (C++) frames and JavaScript frames. It can be used on a running Node.js application or through a core dump.
-
How to debug programs in console? (C program for example)
An alternative to gdb is lldb. But I like gdb.
-
How to Debug WASI Pipelines with ITK-Wasm
The CMake-based, itk-wasm build system tooling enables the same C++ build system configuration and code to be reused when building a native system binary or a WebAssembly binary. As a result, native binary debugging tools, such as GDB, LLDB, or the Visual Studio debugger can be utilized.
-
What is the debug drawer?
The debugger component of the LLVM project. It’s what you’re typing into when you type po someExpression. https://lldb.llvm.org/ Web searches could help explain a lot of this for you 😊
-
Best debugger for windows? GDB is not stable and can't seem to find an alternative.
If you really don't want to touch Visual Studio/MSVC then you can try to compile with clang and use lldb: https://lldb.llvm.org/
-
dap: configuration to automatically launch codelldb server
LLDB - https://lldb.llvm.org/ - Debugger from the LLVM project
-
Debugging with GDB
Well, there's LLDB (https://lldb.llvm.org/) - I've heard it's got some nifty architectural features (e.g. having access to the Clang framework for handling C/C++ expressions).
I've done some minimal poking about in the code; I found its object-orientation a bit hard to grok (just for me personally) but it seemed to be quite uniformly applied so it might well be easier to work with.
-
Write your GDB scripts in Haskell
The article does mention lldb as a future target.
-
Kdevelop: Debug, "Could not run 'lldb-mi'
check if lldb-mi comes with lldb in your package manager. if not build it form here: https://github.com/lldb-tools/lldb-mi.
clasp
-
I Accidentally a Scheme
I accidentally a Common Lisp that interoperates with C++ (https://github.com/clasp-developers/clasp.git). We would also like to move beyond BDWGC and Whiffle looks interesting. I will reach out to you and maybe we can chat about it.
-
Val, a high-level systems programming language
Clasp might be such a language, it seems.
https://github.com/clasp-developers/clasp
-
The jank programming language (by Jeaye Wilkerson)
/u/jeaye are you aware of CLASP? https://github.com/clasp-developers/clasp https://www.youtube.com/watch?v=mbdXeRBbgDM
- Clasp v2.3.0 · Bytecode compiled images, preliminary Apple Silicon support, LLVM16.
-
Proof of Concept clang plugin that automatically binds C/C++ -> Lua
Sounds to me like CLASP; it automatically exports C++ objects to be used from Common Lisp also via llvm.
-
Running Lisp in production @ grammarly
Now, the difference of compiling speed of SBCL and CCL is not so big. Look at cl-benchmark, LispWorks is really fast, CCL is on par with Allegro, SBCL is close to CCL. Or https://github.com/clasp-developers/clasp/wiki/Relative-Compile-Performance-of-clasp, it depends on specific project (SBCL sometimes faster, slower, alike), overall difference is not big.
-
What help is needed for Lisp community in order to make Lisp more popular?
So..
"Why do you want to make Lisp more popular? If you were sucessful, what would be different in the world, and why is that desirable to you?"
Normally at this point I'd listen to the response, and ask more questions based on that. That would wind up with a very, very deep thread, so I'll break a cardinal rule and pre-guess at some answers.
This kind of question comes up pretty frequently. In many cases, I suspect the motivation behind the question is "Wow! Here's this cool tool I've discovered. I want to make something really useful with it. I want to do it as part of a community effort; share my excitement with others, share in their excitement, and know that what I'm making is useful because others find it desirable and are excited by it." The field could be cooking, sports, old machine tools, tiny homes, or demo scene. Its the fundemental driver for most content on HN, YouTube, Instructables, and such. It is a Good Thing.
If that is your motivator, then my suggestion is to find something that bugs you and fix it. You've already decided you're only interested in code, not other aspects. You said you preferred vim, but the emacs ecosystem has a very rich set of sharp edges that need filing off, and a rich set of tools with which to attack them.
One example: even after 50 years there's no open IDE which allows you to easily globally rename a Lisp identifier. I don't know about LispWorks or other proprietary environments, but you can't in emacs or vim do a right-click on "foo" in "(defun foo ()...)" and select a command which automatically renames it in all invocations. [Queue lots of "but you can..." replies here.] I don't think vim is up to the task of doing this internally. It would be possible in emacs; but would require a huge effort with lots of help from other people. If you emerged alive from that rabbit warren you'd join the company of Certified "How Hard Could it Be?" Mad Scientists such as Dr. "I just want to draw molecules" Meister [1] and "Wouldn't an OS in Lisp be Cool" Froggey [2].
[1] https://github.com/clasp-developers/clasp
[2] Mezzano https://github.com/froggey/Mezzano
-
Linux Kernel 6.1 Released with Initial Rust Code
But also, there's a reason why most implementations readily make an effort to provide interoperability tools with a variety of runtimes. Clasp much like ABCL gives access to a whole library of other libraries trivially wrapped to interoperate with at little to no performance to cost (depending on how thin you make the wrappers, mainly).
- Common Lisp Clasp v2.0.0 released
What are some alternatives?
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
Wren - The Wren Programming Language. Wren is a small, fast, class-based concurrent scripting language.
gdb-dashboard - Modular visual interface for GDB in Python
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
CL-CXX-JIT - Common Lisp and CXX interoperation with JIT
CodeLLDB - A native debugger extension for VSCode based on LLDB
SICL - A fresh implementation of Common Lisp
rr - Record and Replay Framework
graalvm-clojure - This project contains a set of "hello world" projects to verify which Clojure libraries do actually compile and produce native images under GraalVM.
voltron - A hacky debugger UI for hackers
maru - Maru - a tiny self-hosting lisp dialect