#lldb — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lldb, aggregated by home.social.
-
I notice I'm finding fun puzzles in playing with #lldb more and finding out what actually is being called in AppKit
-
I notice I'm finding fun puzzles in playing with #lldb more and finding out what actually is being called in AppKit
-
[#Compiler] Day 1 of #AoCO2025 Study Notes
While the original uses #CompilerExplorer, I wanted to replicate the analysis locally.
In this post, I have used #gcc, #clang, llvm-objdump and #LLDB to analyze.
Read more here: https://gapry.github.io/2026/01/01/Advent-of-Compiler-Optimisations-Study-Notes-01.html
-
Как я в 15 лет собрал LLVM ToolChain на Windows без MSVC
Как собрать актуальный LLVM со всеми рантаймами (Clang, LLD, LLDB, CLANG-EXTRA-TOOLS) нативно под Windows, если WinLibs перестал обновляться, а другие сборки не подходят? В этой статье я расскажу о своем 4-месячном пути: от накоплений со школьных обедов на первый ПК до борьбы с линковкой библиотек и поиска фиксов в экспериментальной ветке LLVM 22. История о том, почему я выбрал путь «чистого Upstream» и как заставил это всё работать в 15 лет. Заинтересовало
https://habr.com/ru/articles/980942/
#C++ #llvm #clang #lld #lldb #clangextratools #mingww64 #Сборка #Без_MSVC
-
Bypassing #iOS Frida Detection with #LLDB and #Frida
https://tonygo.tech/blog/2025/8ksec-ios-ctf-writeup -
We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):
We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.
We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.
Let me know if you're interested!
EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).
We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.
EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!
EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!
-
We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):
We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.
We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.
Let me know if you're interested!
EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).
We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.
EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!
EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!
-
🎉 Behold, yet another attempt to make #debugging "fun" by ditching the decades-old, well-established #GDB and #LLDB for a shiny terminal interface. Because who needs reliable tools when you can have a hipster debugger that promises to revolutionize... absolutely nothing? 🙃
https://github.com/al13n321/nnd #fun #terminalinterface #hipsterdebugger #HackerNews #ngated -
🎉 Behold, yet another attempt to make #debugging "fun" by ditching the decades-old, well-established #GDB and #LLDB for a shiny terminal interface. Because who needs reliable tools when you can have a hipster debugger that promises to revolutionize... absolutely nothing? 🙃
https://github.com/al13n321/nnd #fun #terminalinterface #hipsterdebugger #HackerNews #ngated -
Nnd – a TUI debugger alternative to GDB, LLDB
-
Nnd – a TUI debugger alternative to GDB, LLDB
-
Finally I got debugging with nvim, clang and lldb working in Neovim. Including preLaunchTasks, CMakePresets...
Now I need to clean up the build process.
One thing that seems absolutely essential is to add the nvim-dap-lldb to the mix.
But for now it just works and I can move on from here.
#gamedev #neovim #cpp #clang #lldb #linux #vulkan -
Finally I got debugging with nvim, clang and lldb working in Neovim. Including preLaunchTasks, CMakePresets...
Now I need to clean up the build process.
One thing that seems absolutely essential is to add the nvim-dap-lldb to the mix.
But for now it just works and I can move on from here.
#gamedev #neovim #cpp #clang #lldb #linux #vulkan -
[Перевод] Отладка приложения, которое не хочет, чтобы его отлаживали
Недавно я столкнулся с приложением , которое: Блокирует прикрепление к нему отладчиков. Выполняет преждевременный выход при попытках инъецирования кода. Приводит к вылету телефона целиком, если запустить её со включённым джейлбрейком (!). По последнему пункту: кто вообще так делает??? Всё, что мы делаем (например, выполняем моддинг TikTok , чтобы он показывал только видео с котиками, или устраняем торможения в чужих приложениях), требует возможности исследования работы приложения. Но в приложениях для iOS очень часто используются дополнительные защиты от любопытных глаз, например, обнаружение джейлбрейка или обфускация кода . Похоже, это приложение стало на удивление интересной комбинацией всего перечисленного. Намного более сложной, чем можно было бы ожидать от обычного старого виджет-приложения.
https://habr.com/ru/companies/ruvds/articles/883942/
#ios #обратная_разработка #разработка_под_ios #lldb #flex #frida #патчинг #ruvds_перевод
-
UScope: A New Linux Debugger And Not A GDB Shell, Apparently https://hackaday.com/2025/02/07/uscope-a-new-linux-debugger-and-not-a-gdb-shell-apparently/ #SoftwareDevelopment #LinuxHacks #graphical #debugger #software #linux #LLDB #rust #c++ #gdb #zig #Go
-
UScope: A New Linux Debugger And Not A GDB Shell, Apparently https://hackaday.com/2025/02/07/uscope-a-new-linux-debugger-and-not-a-gdb-shell-apparently/ #SoftwareDevelopment #LinuxHacks #graphical #debugger #software #linux #LLDB #rust #c++ #gdb #zig #Go
-
I like writing articles that help myself not once afterwards.
This case is because of being a rare user of #lldb for #rustlang #debugging.
-
If I was on gdb, that print would have done:
```
(gdb) print &a
$1 = (struct a *) 0x7fffffffe4f8
```which means that I can then use $1 in later expressions to use that value, so then I can do:
```
(gdb) watch $1->a
Watchpoint 2: $1->a
```
and it just works.None of that happens w/ lldb.
And none of the guides that talk about how to convert gdb to lldb mention how to deal w/ these deficiencies.
-
If I was on gdb, that print would have done:
```
(gdb) print &a
$1 = (struct a *) 0x7fffffffe4f8
```which means that I can then use $1 in later expressions to use that value, so then I can do:
```
(gdb) watch $1->a
Watchpoint 2: $1->a
```
and it just works.None of that happens w/ lldb.
And none of the guides that talk about how to convert gdb to lldb mention how to deal w/ these deficiencies.
-
Ok, I just found out that when you print stuff, lldb doesn't actually print things properly.
```
(lldb) run
[...]
-> 10 struct a a = (struct a){};
[...]
Target 0: (t) stopped.
(lldb) print &a
(a *) 0x000000016fdff1b8
(lldb) print ((a *) 0x000000016fdff1b8)->a
error: <user expression 1>:1:6: expected expression
((a *) 0x000000016fdff1b8)->a
^
(lldb) print ((struct a *) 0x000000016fdff1b8)->a
(int) 4266848
```I also just realized that lldb doesn't keep a history of values printed.
-
Ok, I just found out that when you print stuff, lldb doesn't actually print things properly.
```
(lldb) run
[...]
-> 10 struct a a = (struct a){};
[...]
Target 0: (t) stopped.
(lldb) print &a
(a *) 0x000000016fdff1b8
(lldb) print ((a *) 0x000000016fdff1b8)->a
error: <user expression 1>:1:6: expected expression
((a *) 0x000000016fdff1b8)->a
^
(lldb) print ((struct a *) 0x000000016fdff1b8)->a
(int) 4266848
```I also just realized that lldb doesn't keep a history of values printed.
-
First time debugged something small but real with #LLDB
Found the bug purely by accident just because LLDB's interface is so ugly (just different?) compared to what we're all used to in IDEs
-
LLDB does not support reverse debugging yet. As far as I know, there are two ways to implement reverse debugging: one is record and replay, such as the rr tool, which can be considered as read-only; the other is "true" reverse, which can "roll back->modify the state->run again". The latter is not necessarily more useful than the former. For example, some nondeterministic bugs can be reproduced 100% using record and replay, but may not be reproduced by running it again with "true" reverse.
-
I missed #WWDC. Did they mention in the keynote whether they fixed the fucking hardening on lldb? Can I run plugins that call thread_swap_exception_ports() now or what?
-
Working on improving performance for the next #qXmoji release. This will require pre-generating stuff during build (different string formats and probably static hashtables), so doing this in #POSIX #shell script isn't feasible any more, therefore working on a data generation tool in #C now.
I'm amazed how #lldb shows me my #Emoji structs while debugging this 😂
-
I'm trying to use #NeoVim almost exclusively for my home projects (I still need Xcode for debugging Metal), but I keep going back to VSCode just for the #debugger.
I've used command line debuggers (#lldb and #gdb) quite a lot but I think this is one of these cases where I want a proper GUI.
nvim-dap doesn't feel right either.
Something like #remedybg would be ideal, but for #macos and lldb.
Any suggestions?
-
Meanwhile released v0.6.2 with a few more (less important) bugfixes ...
... and working on a new feature, parse #SAUCE metadata.
#lldb (which comes with #FreeBSD base) is quite nice for some first testing 😎
SAUCE ref: https://github.com/radman1/sauce
