Fosstodon

1 post1 participant0 posts today

Disconnect3dI will be giving a talk on Pwndbg open source development in ~1h on a local Python meeetup!It will be livestreamed on: <a href="https://www.youtube.com/live/euK_S81Qnuo?si=EhZ-WhnP-4yZRElE" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/live/euK_S81Qnuo?si=EhZ-WhnP-4yZRElE</a><a href="https://infosec.exchange/tags/ctf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ctf</a> <a href="https://infosec.exchange/tags/gdb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gdb</a> <a href="https://infosec.exchange/tags/pwndbg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pwndbg</a> <a href="https://infosec.exchange/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a>

LavX NewsUnveiling Debugging Secrets: How macOS 15.4 Breaks LLDB and What It Means for DevelopersA recent update to macOS 15.4 has uncovered critical issues in the LLDB debugger, revealing hidden internal breakpoints that can impact software development and security. This article dives deep into ...<a href="https://news.lavx.hu/article/unveiling-debugging-secrets-how-macos-15-4-breaks-lldb-and-what-it-means-for-developers" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/unveiling-debugging-secrets-how-macos-15-4-breaks-lldb-and-what-it-means-for-developers</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/Debugging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debugging</a> <a href="https://mastodon.cloud/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> <a href="https://mastodon.cloud/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a>

Habr[Перевод] Отладка приложения, которое не хочет, чтобы его отлаживалиНедавно я столкнулся с приложением , которое: Блокирует прикрепление к нему отладчиков. Выполняет преждевременный выход при попытках инъецирования кода. Приводит к вылету телефона целиком, если запустить её со включённым джейлбрейком (!). По последнему пункту: кто вообще так делает??? Всё, что мы делаем (например, выполняем моддинг TikTok , чтобы он показывал только видео с котиками, или устраняем торможения в чужих приложениях), требует возможности исследования работы приложения. Но в приложениях для iOS очень часто используются дополнительные защиты от любопытных глаз, например, обнаружение джейлбрейка или обфускация кода . Похоже, это приложение стало на удивление интересной комбинацией всего перечисленного. Намного более сложной, чем можно было бы ожидать от обычного старого виджет-приложения.<a href="https://habr.com/ru/companies/ruvds/articles/883942/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://habr.com/ru/companies/ruvds/articles/883942/</a><a href="https://zhub.link/tags/ios" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ios</a> <a href="https://zhub.link/tags/%D0%BE%D0%B1%D1%80%D0%B0%D1%82%D0%BD%D0%B0%D1%8F_%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%BA%D0%B0" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#обратная_разработка</a> <a href="https://zhub.link/tags/%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%BA%D0%B0_%D0%BF%D0%BE%D0%B4_ios" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#разработка_под_ios</a> <a href="https://zhub.link/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a> <a href="https://zhub.link/tags/flex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#flex</a> <a href="https://zhub.link/tags/frida" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frida</a> <a href="https://zhub.link/tags/%D0%BF%D0%B0%D1%82%D1%87%D0%B8%D0%BD%D0%B3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#патчинг</a> <a href="https://zhub.link/tags/ruvds_%D0%BF%D0%B5%D1%80%D0%B5%D0%B2%D0%BE%D0%B4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruvds_перевод</a>

CLion BlogFaster Debugging for Massive MSVC-Based Projects in CLion <a href="https://techhub.social/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> <a href="https://techhub.social/tags/CLion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLion</a> <a href="https://techhub.social/tags/News" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#News</a> <a href="https://techhub.social/tags/Debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debugger</a> <a href="https://techhub.social/tags/Eap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Eap</a> <a href="https://techhub.social/tags/Lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lldb</a> <a href="https://techhub.social/tags/Msvc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Msvc</a><a href="https://blog.jetbrains.com/clion/2025/02/lldb-msvc-improvements/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.jetbrains.com/clion/2025/02/lldb-msvc-improvements/</a>

LavX NewsZig Language Enhancements: A Leap Towards Performance and Debugging ExcellenceThe Zig programming language is undergoing significant enhancements, particularly with its memory allocator and debugging support. These changes not only improve performance but also position Zig as a...<a href="https://news.lavx.hu/article/zig-language-enhancements-a-leap-towards-performance-and-debugging-excellence" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/zig-language-enhancements-a-leap-towards-performance-and-debugging-excellence</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/MemoryManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MemoryManagement</a> <a href="https://mastodon.cloud/tags/ZigLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZigLang</a> <a href="https://mastodon.cloud/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a>

Pyrzout :vm:UScope: A New Linux Debugger And Not A GDB Shell, Apparently <a href="https://hackaday.com/2025/02/07/uscope-a-new-linux-debugger-and-not-a-gdb-shell-apparently/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackaday.com/2025/02/07/uscope-a-new-linux-debugger-and-not-a-gdb-shell-apparently/</a> <a href="https://social.skynetcloud.site/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDevelopment</a> <a href="https://social.skynetcloud.site/tags/LinuxHacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxHacks</a> <a href="https://social.skynetcloud.site/tags/graphical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#graphical</a> <a href="https://social.skynetcloud.site/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> <a href="https://social.skynetcloud.site/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#software</a> <a href="https://social.skynetcloud.site/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://social.skynetcloud.site/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a> <a href="https://social.skynetcloud.site/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://social.skynetcloud.site/tags/c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#c</a>++ <a href="https://social.skynetcloud.site/tags/gdb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gdb</a> <a href="https://social.skynetcloud.site/tags/zig" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zig</a> <a href="https://social.skynetcloud.site/tags/Go" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Go</a>

Pedro PiñeraWe really want to take automation in Swift Package and Xcode projects into a better place:1. You should be able to build and test your projects in the most optimal way and get telemetry to improve things. 2. You should be able to extend automation with your own workflows in Swift and be able to debug them with <a href="https://mastodon.pepicrft.me/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a> 3. You should be able to virtualise the execution of the workflows locally. 4. You should be able to run workflows virtualised in a remote environment like you did locally.

Karol MazurekFresh article on how to build, <a href="https://infosec.exchange/tags/RE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RE</a>, <a href="https://infosec.exchange/tags/debug" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debug</a>, and <a href="https://infosec.exchange/tags/recon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#recon</a> <a href="https://infosec.exchange/tags/XPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XPC</a> services on <a href="https://infosec.exchange/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> with an <a href="https://infosec.exchange/tags/XCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XCode</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> walkthrough (<a href="https://infosec.exchange/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> and <a href="https://infosec.exchange/tags/NSXPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NSXPC</a> APIs). Plus actual <a href="https://infosec.exchange/tags/debugging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugging</a> tips with <a href="https://infosec.exchange/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a>. If you are into <a href="https://infosec.exchange/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a>/#iOS, this one's for you - <a href="https://infosec.exchange/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a> included. Enjoy!<a href="https://karol-mazurek.medium.com/xpc-programming-on-macos-7e1918573f6d?sk=v2%2F21c4e9c7-40a5-43dd-804b-0d8f9bc4e94c" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://karol-mazurek.medium.com/xpc-programming-on-macos-7e1918573f6d?sk=v2%2F21c4e9c7-40a5-43dd-804b-0d8f9bc4e94c</a>

Luke T. ShumakerIn <a href="https://fosstodon.org/tags/lldb" class="mention hashtag" rel="tag">#lldb</a> by default a backtrace shows not just the $pc and function name, but also which objfile that pc/func are in. Like "exename" or "libc.so" or whatever. Is there a way to get <a href="https://fosstodon.org/tags/gnu" class="mention hashtag" rel="tag">#gnu</a> <a href="https://fosstodon.org/tags/gdb" class="mention hashtag" rel="tag">#gdb</a> to do this? (Or am I going to have to submit a patch myself? :P )

yugaego 🌍I like writing articles that help myself not once afterwards.This case is because of being a rare user of <a href="https://fosstodon.org/tags/lldb" class="mention hashtag" rel="tag">#lldb</a> for <a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="tag">#rustlang</a> <a href="https://fosstodon.org/tags/debugging" class="mention hashtag" rel="tag">#debugging</a>.<a href="https://blog.ego.team/programming/rust-debugger-intro.html" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://blog.ego.team/programming/rust-debugger-intro.html</a>

John-Mark GurneyIf 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.<a href="https://flyovercountry.social/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a>

John-Mark GurneyOk, 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.<a href="https://flyovercountry.social/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a>

CLion BlogCLion 2024.3 EAP 3: OpenCV Image Viewer and the Ability to Attach the Debugger to an Unstarted Process <a href="https://techhub.social/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> <a href="https://techhub.social/tags/CLion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLion</a> <a href="https://techhub.social/tags/Eap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Eap</a> <a href="https://techhub.social/tags/News" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#News</a> <a href="https://techhub.social/tags/Clionnova" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clionnova</a> <a href="https://techhub.social/tags/Debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debugger</a> <a href="https://techhub.social/tags/Gdb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gdb</a> <a href="https://techhub.social/tags/Lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lldb</a> <a href="https://techhub.social/tags/Opencv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opencv</a><a href="https://blog.jetbrains.com/clion/2024/10/2024-3-eap-3/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.jetbrains.com/clion/2024/10/2024-3-eap-3/</a>

🅴🆁🆄🅰 🇷🇺Про контейнеризацию в разработке софта. Порой имеется несколько разных #<a class="" href="https://hub.hubzilla.de/search?tag=linux" rel="nofollow noopener noreferrer" target="_blank">linux</a> (и дистрибутивов и версий) под которые надо разрабатывать приложения (собирая, отлаживая). Либо локально на машине разработчика или же на серверах каких-то. Как вариант, берётся #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> с <a href="https://code.visualstudio.com/docs/devcontainers/containers" rel="nofollow noopener noreferrer" target="_blank">предлагаемым подходом</a> и даже есть более-менее <a href="https://code.visualstudio.com/docs/devcontainers/tutorial" rel="nofollow noopener noreferrer" target="_blank">подробная информация</a> для освоения процесса. Для чего берётся вот это расширение <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers" rel="nofollow noopener noreferrer" target="_blank">Dev Containers</a>. И в контейнер ходит не через #<a class="" href="https://hub.hubzilla.de/search?tag=SSH" rel="nofollow noopener noreferrer" target="_blank">SSH</a>, а производит установку внутрь контейнера такой вещи как «VSCode Server». Выполняется установка прозрачно для пользователя, в процессе «подключения» к заданному контейнеру (на локальной машине). #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> берёт идентификатор своей версии (commit id) и по нему скачивает «VSCode Server» со специального сайта #<a class="" href="https://hub.hubzilla.de/search?tag=Microsoft" rel="nofollow noopener noreferrer" target="_blank">Microsoft</a>. А само окно #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> становится чем-то вроде удалённого GUI для того сервера, что теперь запущен в контейнере. Приколов несколько:<ul><li> В таком открывшемся окне #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> на вкладке расширений придётся включить уже имеющиеся/установленные расширения, чтобы они скопировались внутрь контейнера. Т.е. работают он реально там на сервере, а не тут локально.</li><li> Некоторым расширениям нужны всякие вещи, вроде #<a class="" href="https://hub.hubzilla.de/search?tag=LSP" rel="nofollow noopener noreferrer" target="_blank">LSP</a> сервера, #<a class="" href="https://hub.hubzilla.de/search?tag=lldb" rel="nofollow noopener noreferrer" target="_blank">lldb</a> / #<a class="" href="https://hub.hubzilla.de/search?tag=gdb" rel="nofollow noopener noreferrer" target="_blank">gdb</a>, иногда <a href="https://github.com/lldb-tools/lldb-mi" rel="nofollow noopener noreferrer" target="_blank">lldb-mi</a>. Всё это внутрь контейнера придётся устанавливать самостоятельно, ручками.</li><li> Использовать расширение <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers" rel="nofollow noopener noreferrer" target="_blank">Dev Containers</a> получится лишь на официальной Visual Studio Code — в таких вариантах как #<a class="" href="https://hub.hubzilla.de/search?tag=Code-OSS" rel="nofollow noopener noreferrer" target="_blank">Code-OSS</a>, #<a class="" href="https://hub.hubzilla.de/search?tag=VSCodium" rel="nofollow noopener noreferrer" target="_blank">VSCodium</a> и #<a class="" href="https://hub.hubzilla.de/search?tag=Uncoded" rel="nofollow noopener noreferrer" target="_blank">Uncoded</a> оно просто не доступно. А если его установить через скаченный #<a class="" href="https://hub.hubzilla.de/search?tag=VSIX" rel="nofollow noopener noreferrer" target="_blank">VSIX</a>, то работать не будет.</li></ul> Хорошо или плохо? Официальный #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> конечно же шлёт телеметрию в #<a class="" href="https://hub.hubzilla.de/search?tag=Microsoft" rel="nofollow noopener noreferrer" target="_blank">Microsoft</a> «со страшной силой» да и вообще, является проприетарным вариантом дистрибьюции #<a class="" href="https://hub.hubzilla.de/search?tag=Code-OSS" rel="nofollow noopener noreferrer" target="_blank">Code-OSS</a>, который тоже, в свою очередь, страдает телеметрией (из-за чего и появились #<a class="" href="https://hub.hubzilla.de/search?tag=VSCodium" rel="nofollow noopener noreferrer" target="_blank">VSCodium</a> да #<a class="" href="https://hub.hubzilla.de/search?tag=Uncoded" rel="nofollow noopener noreferrer" target="_blank">Uncoded</a> ). Однако, именно в силу проприетарности #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> и позволяет из галереи устанавливать проприетарное же расширение <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers" rel="nofollow noopener noreferrer" target="_blank">Dev Containers</a>. А в галереи у #<a class="" href="https://hub.hubzilla.de/search?tag=Code-OSS" rel="nofollow noopener noreferrer" target="_blank">Code-OSS</a> этого расширения нет и понятно почему — не сможет скачать серверную часть, которую нужно устанавливать внутри контейнера (в качестве агента) и которая тоже проприетарная. В целом: <ul><li> Работать с кодом получается, равно как и обычным образом, как если бы тулчейн и библиотеки не находились внутри контейнера;</li><li> Поддерживаются как обычные #<a class="" href="https://hub.hubzilla.de/search?tag=Docker" rel="nofollow noopener noreferrer" target="_blank">Docker</a> -контейнеры так и #<a class="" href="https://hub.hubzilla.de/search?tag=rootless" rel="nofollow noopener noreferrer" target="_blank">rootless</a> варианты контейнеров — соответственно, и #<a class="" href="https://hub.hubzilla.de/search?tag=Podman" rel="nofollow noopener noreferrer" target="_blank">Podman</a> -контейнеры тоже (которые априори #<a class="" href="https://hub.hubzilla.de/search?tag=rootless" rel="nofollow noopener noreferrer" target="_blank">rootless</a> );</li><li> Не обязательно заморачиваться с <code>.devcontainer/devcontainer.json</code> в проекте, можно подключаться из #<a class="" href="https://hub.hubzilla.de/search?tag=VSCode" rel="nofollow noopener noreferrer" target="_blank">VSCode</a> к любому контейнеру — запустится новое окно редактора.</li></ul> Нормальный проприетарный продукт, охватывает разные сценарии. В том числе и для любителей сидеть на #<a class="" href="https://hub.hubzilla.de/search?tag=Windows" rel="nofollow noopener noreferrer" target="_blank">Windows</a> и вести разработку через #<a class="" href="https://hub.hubzilla.de/search?tag=WSL" rel="nofollow noopener noreferrer" target="_blank">WSL</a> (Windows Subsystem for Linux v2). Чтобы работало с #<a class="" href="https://hub.hubzilla.de/search?tag=rootless" rel="nofollow noopener noreferrer" target="_blank">rootless</a> контейнерами надо в: <code>~/.config/Code/User/settings.json</code> прописать параметры вида: <pre><code>"dev.containers.dockerSocketPath": "unix:///run/user/100500/docker.sock", "docker.environment": {     "DOCKER_HOST": "unix:///run/user/100500/docker.sock" },</code></pre>Подсмотреть unix-socket можно через: <pre><code>$ systemctl status --user docker.socket ...      Listen: /run/user/100500/docker.sock (Stream)</code></pre> #<a class="" href="https://hub.hubzilla.de/search?tag=vscode" rel="nofollow noopener noreferrer" target="_blank">vscode</a> #<a class="" href="https://hub.hubzilla.de/search?tag=containerization" rel="nofollow noopener noreferrer" target="_blank">containerization</a> #<a class="" href="https://hub.hubzilla.de/search?tag=containers" rel="nofollow noopener noreferrer" target="_blank">containers</a> #<a class="" href="https://hub.hubzilla.de/search?tag=softwaredevelopment" rel="nofollow noopener noreferrer" target="_blank">softwaredevelopment</a> #<a class="" href="https://hub.hubzilla.de/search?tag=software" rel="nofollow noopener noreferrer" target="_blank">software</a> #<a class="" href="https://hub.hubzilla.de/search?tag=lang_ru" rel="nofollow noopener noreferrer" target="_blank">lang_ru</a> @<a href="https://3zi.ru/@Russia" rel="nofollow noopener noreferrer" target="_blank">Russia</a> @<a href="https://newsmast.community/@programming" rel="nofollow noopener noreferrer" target="_blank">Programming Feed</a>

nutilius@SDFSo problem seems to be solved. The reason was in different initiation of memory data structures. I wrongly assumed that structure was zeroed. Now it works without any problem. But <a href="https://social.sdf.org/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> <a href="https://social.sdf.org/tags/LLDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLDB</a> still cannot attach to running process, breaks with `Out of memory` and core dump. Maybe I should look Ito that core … using LLDB 😂.

Felix Palmen :freebsd: :c64:<a href="https://mastodon.bsd.cafe/@matuzalem" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@matuzalem</a> here's a release to test 😉 I'm pretty sure it won't crash, but can't guarantee. It's been examined a lot, also with <a href="https://mastodon.bsd.cafe/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a> and <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valgrind</a>, but doesn't have any automated tests so far. I'm still undecided about investing the time and effort to change that, would need to pick a library/framework first (C doesn't offer any testing capabilities in the language) and then, while a few modules like the unicode string functions are perfectly unit-testable, the whole project is a large "event processor" (like any GUI application) and depends on these external events, so a *lot* of tedious mocking would be required for better test coverage ...edit: btw, fixed a weird bug before releasing this, it was possible to enter a state where processing X11 events stopped (requesting to minimize with the WM ignoring the request). Not a crash, but a bug 😅

:rss: Hacker NewsHow Conditional Breakpoints Work <a href="https://werat.dev/blog/how-conditional-breakpoints-work/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://werat.dev/blog/how-conditional-breakpoints-work/</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://rss-mstdn.studiofreesia.com/tags/developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developer</a> <a href="https://rss-mstdn.studiofreesia.com/tags/personal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#personal</a> <a href="https://rss-mstdn.studiofreesia.com/tags/debugging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugging</a> <a href="https://rss-mstdn.studiofreesia.com/tags/debuggers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debuggers</a> <a href="https://rss-mstdn.studiofreesia.com/tags/visual_studio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#visual_studio</a> <a href="https://rss-mstdn.studiofreesia.com/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a> <a href="https://rss-mstdn.studiofreesia.com/tags/expression_evaluation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#expression_evaluation</a> <a href="https://rss-mstdn.studiofreesia.com/tags/lldb_eval" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb_eval</a> <a href="https://rss-mstdn.studiofreesia.com/tags/raddbg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raddbg</a> <a href="https://rss-mstdn.studiofreesia.com/tags/delve" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#delve</a>

Felix Palmen :freebsd: :c64:<a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#X11</a> <a href="https://mastodon.bsd.cafe/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> with <a href="https://mastodon.bsd.cafe/tags/xcb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xcb</a>, tales of the quest ... 🧐So yes, there were still bugs. And despite (optional) extensive trace logging, I needed a <a href="https://mastodon.bsd.cafe/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugger</a> to really understand what was going on. So, did the following:- launch from within lldb - do some preparations to get close to the "buggy" behavior - interrupt, set a breakpoint, continue - click something, breakpoint gets hit - oh 😡 --- mouse is grabbed 🙈This is effectively a deadlock of your X session. Your program, stopped by the debugger, is never able to release the grab. and you can't resume it because with the grab in place, there's no way to focus the <a href="https://mastodon.bsd.cafe/tags/xterm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xterm</a> running <a href="https://mastodon.bsd.cafe/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a>. 🤦Note to self: When debugging your X11 program, always have the controlling terminal for the debugger outside the X session used for debugging. Of course, the most convenient solution here is once again <a href="https://mastodon.bsd.cafe/tags/Xephyr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xephyr</a> 😉

lambdageekcontext: <a href="https://github.com/dotnet/diagnostics/issues/4551" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/dotnet/diagnostics/issues/4551</a><a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a> <a href="https://mastodon.social/tags/mach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mach</a> <a href="https://mastodon.social/tags/hardenedRuntime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hardenedRuntime</a>

lambdageekI missed <a href="https://mastodon.social/tags/WWDC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WWDC</a>. 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?<a href="https://mastodon.social/tags/lldb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lldb</a> <a href="https://mastodon.social/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a>

Recent searches

Search options

Administered by:

Server stats:

#lldb