Es ist echt nützlich, Debuggin-Sessions vollständig durchzuskripten und automatisch Befehle bei Breakpoints auszuführen 🤔
Es ist echt nützlich, Debuggin-Sessions vollständig durchzuskripten und automatisch Befehle bei Breakpoints auszuführen 🤔
Dumme Idee des Tages: mit dem Debugger einen Breakpoint setzen und in diesem automatisch eine VM starten 🫠
🤔 Ah, the riveting saga of the #GDB #JIT interface, where we discover that #debugging JIT-compiled code is as clear as mud without #DWARF sprinkles. 🐢 Because who wouldn't want to step through machine code one agonizing instruction at a time while GDB plays the clueless sidekick? 🤷♂️🔧
https://bernsteinbear.com/blog/gdb-jit/ #JITCompilation #DebuggingChallenges #CodingSaga #HackerNews #ngated
The GDB JIT Interface
https://bernsteinbear.com/blog/gdb-jit/
#HackerNews #GDB #JIT #Interface #GDB #Debugging #Just-In-Time #Compilation #Software #Development
Good day! my first try at contributing to #gdb
Fixing crash in #debian #trixie on absent working directory.
https://sourceware.org/pipermail/gdb-patches/2026-January/224101.html
GNU Toolchain Office Hours Europe/Americas starting now!
GNU Toolchain Office Hours starting soon!
Europe/Americas: Thursday, Jan 15 at 8:00 AM PST / 11:00 AM EST / 16:00 CET
GNU Toolchain Office Hours Asia/Pacific starting now!
GNU Toolchain Office Hours Asia/Pacific starting in 30 minutes!
Thursday Jan 15 at 09h00 IST / 11:30 AM CST / 12:30 PM JST/ 2:30 PM AEDT / 10:30 PM EST (14 Jan) / 7:30 PM PST (14 Jan)
GNU Toolchain Office Hours Asia/Pacific starting soon!
Thursday Jan 15 at 09h00 IST / 11:30 AM CST / 12:30 PM JST/ 2:30 PM AEDT / 10:30 PM EST (14 Jan) / 7:30 PM PST (14 Jan)
🚀 Calling all open source enthusiasts! Join the monthly GNU Toolchain Office Hours for deep dives into GCC, Binutils, GDB, GLIBC, and more.
Whether you're debugging, optimizing, or contributing—let's collaborate!
Asia/Pacific: Thursday Jan 15 at 09h00 IST / 11:30 AM CST / 12:30 PM JST/ 2:30 PM AEDT / 10:30 PM EST (14 Jan) / 7:30 PM PST (14 Jan)
Europe/Americas: Thursday, Jan 15 at 8:00 AM PT / 11:00 AM ET / 16:00 CET
How I solve my problems:
Пошаговая GDB отладка прошивки STM32 из консоли cmd
Порой бывает так, что вы скачиваете open-source репозиторий, а там нет файлов .project и .сproject для eclipse или файлы .project и .сproject есть, но они по каким-то причинам повреждены и IDE их не может открыть. Тем не менее прошивка собирается командой make all. Ты ее прошиваешь и LED не мигает. Очевидно, что прошивка зависла. Где-то свалилась в HardFault_Handler. В этом случае надо просто взять и запускать пошаговую отладку из консоли . Это классический способ разобраться, где же произошла осечка.
https://habr.com/ru/articles/979122/
#stm32 #gdb #elf #cli #cmd #gdbserver #gdbclient #gcc #stlink #gnu
🌘 使用 GDB 辨識 Arm Cortex-M 的當前安全狀態
➤ 透過堆疊指標數值比對,快速掌握 TrustZone 運行切換
✤ https://danielmangum.com/posts/arm-cortex-m-security-state-gdb/
在嵌入式系統開發中,調試具備 TrustZone(Armv8-M 安全擴充功能)的處理器(如 Arm Cortex-M33)常面臨一項挑戰:如何快速判斷處理器目前正處於「安全(Secure)」還是「非安全(Non-Secure)」狀態。開發者 Daniel Mangum 提供了一個簡潔高效的方案。由於處理器在不同安全狀態下會使用各自獨立的堆疊指標(Stack Pointer, SP),我們只需透過 GDB 同時讀取當前的 SP 以及各個堆疊指標變體(MSP_S, MSP_NS 等),並進行數值比對,就能即時揭示處理器的運行環境。這種方法在處理如 Zephyr RTOS 等複雜的多執行緒系統時,能顯著提升排錯效率。
+ 「這是在處理
#嵌入式系統 #Arm Cortex-M #GDB 調試 #TrustZone #韌體開發
Determining Current Arm Cortex-M Security State with GDB
https://danielmangum.com/posts/arm-cortex-m-security-state-gdb/
#HackerNews #ArmCortexM #GDB #SecurityState #EmbeddedSystems #Cybersecurity #TechNews
The GDB JIT interface
Max Bernstein
https://bernsteinbear.com/blog/gdb-jit/
I wonder if there are existing tools working with this kind of concept that would also include the more difficult parts, such as 3D camera movements, etc.
That's not my objective for now though, I just needed to display images and I got them with like an hour of work, I found and fixed my bug, and now I have the tools to do it again if needed.
Another lead that I have not explored would be to add a "pretty-printer" in #GDB that could display an image. Not sure if that's even possible?
Petite forme 🥲
#lendemain #gdb #dimanche