From 1a8d5c728cc275f20d7f560e2760aa882c8ed502 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 4 Nov 2018 16:09:55 +0100 Subject: Fix hurd-dbgsym packagename --- faq/debugging_translators.mdwn | 2 +- gdb/backtrace.mdwn | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/faq/debugging_translators.mdwn b/faq/debugging_translators.mdwn index 3cb4a2ef..1bd0deec 100644 --- a/faq/debugging_translators.mdwn +++ b/faq/debugging_translators.mdwn @@ -12,7 +12,7 @@ License|/fdl]]."]]"""]] [[!tag faq/development]] In order to [[debug|debugging]] translators and being able to step into glibc -during it, on Debian you need the `hurd-dbg` and `libc0.3-dbg` packages installed. +during it, on Debian you need the `hurd-dbgsym` and `libc0.3-dbg` packages installed. If you need to debug the initialization of the translator, start the translator like diff --git a/gdb/backtrace.mdwn b/gdb/backtrace.mdwn index 7411ad05..e4f94b72 100644 --- a/gdb/backtrace.mdwn +++ b/gdb/backtrace.mdwn @@ -25,5 +25,5 @@ Run the faulting program like this: libraries) contain debugging symbols, or those are available separartely. If you're one a [[Debian_GNU/Hurd_system|hurd/running/debian]], you'll have -to have the *hurd-dbg* package installed for debugging Hurd stuff, and perhaps +to have the *hurd-dbgsym* package installed for debugging Hurd stuff, and perhaps *libc0.3-dbg* as well if it's inside the glibc. -- cgit v1.3.1