sys-devel/gdb/ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

# $Header: /var/cvsroot/gentoo-x86/sys-devel/gdb/ChangeLog,v 1.8 2002/10/11 20:29:14 raker Exp $

*gdb-5.2.1 (20 Aug 2002)

  11 Oct 2002; Nick Hadaway <raker@gentoo.org> gdb-5.2.1.ebuild :
  Throttled optimization flags down to -O2.  See bug #6089

  20 Aug 2002; Nick Hadaway <raker@gentoo.org>
  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 <gerk@gentoo.org> :
  Added ppc to keywords

  2 June 2002; Olivier Reisch <doctomoe@gentoo.org> 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 <kain@kain.org> 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 <seemant@gentoo.org> 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 <karltk@gentoo.org>: 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 <gbevin@gentoo.org> 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.