# ChangeLog for sys-devel/gdb # Copyright 2002 Gentoo Technologies, Inc. Distributed under the GPL, v2 # $Header: /var/cvsroot/gentoo-x86/sys-devel/gdb/ChangeLog,v 1.10 2002/12/09 04:37:27 manson Exp $ \* Autoupdate keywords (12-6-02) 06 Dec 2002; Rodney Rees changed sparc ~sparc keywords *gdb-5.2.1 (20 Aug 2002) 19 Oct 2002; Seemant Kulleen : cleanup of old ebuilds and formatting. 11 Oct 2002; Nick Hadaway gdb-5.2.1.ebuild : Throttled optimization flags down to -O2. See bug #6089 20 Aug 2002; Nick Hadaway gdb-5.2.1.ebuild, files/digest-gdb-5.2.1, files/man.diff : Version bump. *gdb-5.1.1-r2 (2 June 2002) 24 Jul 2002; Mark Guertin : Added ppc to keywords 2 June 2002; Olivier Reisch gdb-5.1.1-r2.ebuild Have the PPC patch only applied on PPC platform. *gdb-5.1.1-r1 (6 May 2002) 6 May 2002; Kain gdb-5.1.1-r1.ebuild PPC compatibility patch to fix some bool typedef stuff. *gdb-5.1.1 (5 Apr 2002) 5 Apr 2002; Seemant Kulleen gdb-5.1.1.ebuild files/digest-gdb-5.1.1 Version bump, but this is being masked until the ncurses incompatibility is resolved. *gdb-5.1 (7 Feb 2002) Karl Trygve Kalleberg : gdb-5.1.ebuild files/digest-gdb-5.1 GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed. GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act: * Start your program, specifying anything that might affect its behavior. * Make your program stop on specified conditions. * Examine what has happened, when your program has stopped. * Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another. GDB works on a wide variety of UNIX and non-UNIX systems. *gdb-5.0-r2 (1 Feb 2002) 1 Feb 2002; G.Bevin ChangeLog : Added initial ChangeLog which should be updated whenever the package is updated in any way. This changelog is targetted to users. This means that the comments should well explained and written in clean English. The details about writing correct changelogs are explained in the skel.ChangeLog file which you can find in the root directory of the portage repository.