# gdb GDB is the GNU Project debugger, a tool for inspecting and controlling programs during execution to help identify bugs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects DevFeed: [postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects]() Original publisher: [Read original article]() Published: 2026-09-06T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [Testing](), [Operating system](), [GitLab](), [Internationalization (i18n)](), [gdb]() Tags: [2026](), [conferences](), [gdb](), [git](), [gitlab](), [i18n](), [infrastructure](), [linux](), [mobile](), [opensource](), [postmarketos](), [testing]() ### AI overview The August 2026 postmarketOS update covers conference appearances and a newly scheduled project conference, infrastructure improvements including faster Git repositories and a new debuginfod server, progress on musl libc collation and internationalization support, and an accepted proposal for an immutable postmarketOS release with improved automated hardware testing. ### Source excerpt Conferences has been the main theme of this month. We had stands at FrOSCon (photo, next to our friends from Phosh), FOSSY (pictured above) as well as DEFCON and the following postmarketOS / Linux Mobile related talks were given: Automated testing of a phone operating system (Luca at FrOSCon) Push-Benachrichtigungen. Dezentral und OpenSource (Daniel G. at FrOSCon) Random Cool Things from postmarketOS (a linux-based mobile OS) (Ranny at DEFCON) Controlling our devices: linux on mobile (Ranny at DEFCON) Besides that we have of course been very busy planning our own conference and are happy to announce that the schedule is now live! For those who did not get a ticket, the event is completely booked now but we are trying to do video recordings and/or live streams so you can watch the talks at home (no promises for that though since this is our first event). If all goes well, we might even follow up with another one next year. For those who will be there, make sure to join the Matrix chat / IRC channel. Organizational OSUOSL, who maintain gitlab.postmarketos.org, have reacted to slowdowns we have observed across the site and made it significantly faster by moving git repositories to SSDs. Thanks, Lance! Paul has joined the infrastructure team. NLnet and NGI Zero Core related news A production debuginfod server for postmarketOS and Alpine was set up, "allowing developers to automatically fetch debug symbols during crash analysis with tools like coredumpctl and gdb" (!9468, sync-debuginfod, milestone 34) An update was posted by Rich on the collation + i18n support in musl libc project: "I'm pleased to announce a big step in the #musl locale overhaul project: collation is working! This is the result of a long project to design data structures and logic that would admit honoring the full Unicode Collation Algorithm rules, including equivalence under normalization, and keep the size of collation weight tables for the entirety of Unicode under control." And last but not least, ## GNU/Hurd development updates for Q1 2024 DevFeed: [GNU/Hurd development updates for Q1 2024]() Original publisher: [Read original article]() Published: 2024-04-05T11:07:00Z Content type: news Language: en Sources: [GNU Hurd]() Topics: [GNU/Hurd](), [gdb](), [qemu]() Tags: [compiler](), [gdb](), [gnu-hurd](), [qemu](), [test]() ### AI overview The Q1 2024 GNU/Hurd update reports work on keyboard layout support, 64-bit and AArch64 porting, GDB and glibc changes, SMP support, hardware support, testing with QEMU, and a new Alpine-based Hurd distribution in development. ### Source excerpt Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd developments in Q1 of 2024! Details. Etienne Brateau modified console-client to use xkbcommon instead of x11 for xkb extended support, which improves keyboard layout coverage a lot! Flavio Cruz also worked on porting GDB to the 64-bit Hurd, implemented setcontext/getcontext/makecontext/swapcontex () in glibc, and implemented child process resource accounting. The latter implementsgetrusage(RUSAGE_CHILDREN, ) and populates child related data in times(). He fixed the perl testsuite for the Hurd, and he also posted a RFC to enhance tracing utilities, which he used to port the RPC format to 64 bit. Flavio also had a smattering of fixes here, here, here, here, and here. Damien Zammit had some fixes including fixing the console with APIC enabled, patching GNU Mach to support ACPI v2, fixing baud rate on com ports, porting the Hurd to some AMD CPUs (WIP), adding HPET (high precision timers). He also worked on making ext2fs use xattr by default to store translators. Damien also worked on more SMP fixes here, here, here, here, here, and here. Hurd currently boots in SMP mode on the BSP. Damien wrote a test program that lets you run a task on the APs. Sergey Bugaev patched binutils to support the GNU/Hurd on AArch64, and he wrote some patches to make the Hurd easier to port here, here, and here, Sergey also posted a fairly large RFC patch series for his AArch64 port. He writes: MIG seems to just work (thanks to all of Flávio's work!). I'm using the same message ABI as on x86_64, and haven't seen any issues so far -- neither compiler errors / failed static assertions (about struct sizes and such), nor hardware errors from misaligned accesses. He also mentions that "the hardware hardening features (BTI, MTE, PAC) are currently 'not really supported', but I do want to support them in the future." Samuel merged many of the patches. In Sergey's later glibc patch series, he wrote about the AArch64 port progr ## Visualizing Postgres page images within GDB DevFeed: [Visualizing Postgres page images within GDB]() Original publisher: [Read original article]() Author: Peter Geoghegan (noreply@blogger.com) Published: 2019-03-23T00:07:00Z Content type: tutorial Language: en Sources: [Peter Geoghegan's blog]() Topics: [gdb](), [debug](), [debugging](), [Code]() Tags: [command](), [debugging](), [gdb](), [interactive](), [internals](), [pg-hexedit](), [postgresql]() ### AI overview This article explains how to configure GDB to invoke pg_hexedit on PostgreSQL page images without using the filesystem, including images from local temporary buffers. It also describes using a user-defined GDB command during debugging and with core dumps. ### Source excerpt It's straightforward to set up GDB to quickly invoke pg_hexedit on a page image, without going through the filesystem. The page image can even come from a local temp buffer. A user-defined GDB command can be created that shows an arbitrary page image in pg_hexedit from an interactive GDB session. This is a good way to understand what's really going on when debugging access method code. It also works well with core dumps. I found this valuable during a recent project to improve the Postgres B-Tree code. An example of how to make this work is available from a newly added section of the pg_hexedit README file: https://github.com/petergeoghegan/pg_hexedit/#using-pg_hexedit-while-debugging-postgres-with-gdb ## Build an AngrDBG frontend for your debugger DevFeed: [Build an AngrDBG frontend for your debugger]() Original publisher: [Read original article]() Author: malweisse's corruptions Published: 2018-09-22T00:00:00Z Content type: tutorial Language: en Sources: [The blog of malweisse's corruptions]() Topics: [synchronization](), [gdb](), [debug](), [Processes]() Tags: [debugger](), [gdb](), [process](), [python](), [subclass](), [synchronization]() ### AI overview This tutorial explains how to build a frontend for a debugger using AngrDBG. It describes the subclass and registration required to synchronize a concrete process state with an angr state, along with methods for process control, memory and register access, executable metadata, and symbol resolution. ### Source excerpt AngrDBG is the library that I developed to synchronize a concrete process state with an angr state. The library is debugger agnostic. A frontend library that integrates AngrDBG with a specific debugger must implements a subclass of angrdbg.Debugger and register an istance of that class as source of data using angrdbg.register_debugger. The methods that must be implemented are the following: before_stateshot(self) An event handler triggered before the synchronization setup in StateShot, just after the empty state creation after_stateshot(self, state) An event handler triggered before the StateShot return is_active(self) Return True if the debugger is running the target process input_file(self) Return a python file-like object of the target executable image_base(self) Return the process base address get_(self, addr) Read an byte|word|dword|qword from the memory as a python int (4 distinct methods) get_bytes(self, addr, size) Read a string from the memory put_(self, addr, value) Write a python in as a byte|word|dword|qword to the memory (4 distinct methods) put_bytes(self, addr, value) Write a string to the memory get_reg(self, name) Get a register value set_reg(self, name, value) Set a register value step_into(self) Call the debugger step into command run(self) Run the process inside the debugger wait_ready(self) Wait until the debugged process is ready to be inspected refresh_memory(self) Refresh the memory API of the debugger seg_by_name(self, name) Get a Segment object by the name seg_by_addr(self, name) Get a Segment object by the address get_got(self) Get a tuple (start address, end address) related to the GOT section get_plt(self) Get a tuple (start address, end address) related to the PLT section resolve_name(self, name) Resolve a symbol to its address using the name You can find here the GDBDebugger class used in the GDB frontend. ## ReactOS 0.4.0 Released DevFeed: [ReactOS 0.4.0 Released]() Original publisher: [Read original article]() Published: 2016-02-16T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [version](), [CMake](), [gcc](), [MSVC](), [gdb](), [Kernel](), [USB](), [Oracle-VM-VirtualBox](), [networking](), [win32]() Tags: [cmake](), [compiler](), [free](), [gcc](), [gdb](), [kernel](), [msvc](), [networking](), [open-source](), [os](), [react](), [reactos](), [release](), [toolchain](), [usb](), [version](), [virtualbox](), [win32](), [winapi]() ### AI overview The ReactOS Project announces the release of version 0.4.0, highlighting user-facing improvements such as ext2 read/write support, NTFS read support, a new explorer shell, SerialATA, sound, USB, virtualization, and wireless networking. Developer improvements include CMake support for GCC and MSVC, faster compilation, GDB remote kernel debugging, and WinDBG support. ### Source excerpt Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0. A great deal of work has gone into making this release happen and as we look back it is remarkable to consider how far the project has come since that release a decade ago. This release is both a celebration of and a testament to everything that the ReactOS team and community has achieved together. ## Debugging a Difficult HTCondor Logging Bug DevFeed: [Debugging a Difficult HTCondor Logging Bug]() Original publisher: [Read original article]() Published: 2013-05-06T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [bug](), [debug](), [Evergreen ILS](), [Logging](), [gdb](), [Linux](), [Data structures](), [Software](), [Open Source]() Tags: [bugs](), [c-plus-plus](), [code](), [data-structure](), [debug](), [free](), [gdb](), [linux](), [logging](), [open-source](), [os](), [react](), [reactos](), [software](), [win32](), [winapi]() ### AI overview A programmer recounts debugging an HTCondor logging bug that caused a crash through a buffer overflow. Using gdb and valgrind, they traced the problem to a mistaken write involving log-size data stored in a new struct, which could overwrite information used to track log output files. ### Source excerpt In my years working as a programmer, I have run into many, many bugs and introduced many of my own. A few stand out as tremendously irritating to debug, as their behavior made little sense and the source of the bug was non-obvious. The first issue was from my work for the HTCondor Project, an open source cluster management software used by research groups around the world including those working on crunching data from the Large Hadron Collider, the LIGO graviton detector, and the IceCube neutrino observatory. ## Brief GDB Basics DevFeed: [Brief GDB Basics]() Original publisher: [Read original article]() Published: 2012-12-24T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [gdb](), [debugging](), [Software Engineering]() Tags: [code](), [debugger](), [debugging](), [development](), [gcc](), [gdb]() ### AI overview A practical introduction to using gdb for debugging programs that crash, including how to obtain useful stack traces and source locations by compiling with symbols and debug information. ### Source excerpt Introducing a few typical use-cases of gdb for debugging. ## How to crash gdb on OS X DevFeed: [How to crash gdb on OS X]() Original publisher: [Read original article]() Author: Marek Published: 2012-11-12T23:00:00Z Content type: tutorial Language: en Sources: [Marek Majkowski]() Topics: [gdb](), [Kernel](), [Processes]() Tags: [crash](), [gdb](), [hack](), [how-to](), [os](), [process](), [technical]() ### AI overview The article examines why running gdb on iTunes in OS X causes gdb to crash. It attributes the behavior to a process flag that forbids debugging and describes overriding a system call before iTunes invokes it as a workaround. ### Source excerpt How to crash gdb on OS X or how to use gdb on iTunes In recent years the "Apple is evil" discussion started recurring more and more often. In last week's edition on the YCombinator, jrockway mentioned a very interesting technical quirk: [...] I tried to run gdb on iTunes, and gdb segfaulted. I did some research and found that Apple added extra code to the OS just to prevent someone from doing exactly that. They spent additional engineering effort just to lock me out of my own computer.