From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21063 invoked by alias); 4 Aug 2002 19:40:42 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 21046 invoked from network); 4 Aug 2002 19:40:41 -0000 Received: from unknown (HELO sunsite.mff.cuni.cz) (195.113.19.66) by sources.redhat.com with SMTP; 4 Aug 2002 19:40:41 -0000 Received: (from jakub@localhost) by sunsite.mff.cuni.cz (8.11.6/8.11.6) id g74Jecm15923; Sun, 4 Aug 2002 21:40:38 +0200 Date: Sun, 04 Aug 2002 12:40:00 -0000 From: Jakub Jelinek To: Ulrich Drepper Cc: Glibc hackers Subject: [PATCH] manual spelling fix Message-ID: <20020804214038.T20867@sunsite.ms.mff.cuni.cz> Reply-To: Jakub Jelinek Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-SW-Source: 2002-08/txt/msg00049.txt.bz2 Hi! 2002-08-04 Jakub Jelinek * manual/debug.texi: Fix spelling to programmatically. Reported by . --- libc/manual/debug.texi.jj 2001-05-23 09:21:44.000000000 +0200 +++ libc/manual/debug.texi 2002-08-04 21:57:15.000000000 +0200 @@ -26,7 +26,7 @@ locate the problem. A @dfn{backtrace} is a list of the function calls that are currently active in a thread. The usual way to inspect a backtrace of a program is to use an external debugger such as gdb. However, sometimes it is -useful to obtain a backtrace programatically from within a program, +useful to obtain a backtrace programmatically from within a program, e.g., for the purposes of logging or diagnostics. The header file @file{execinfo.h} declares three functions that obtain Jakub