Next | Query returned 35 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2013-02-04 12:05:06 by Makoto Fujiwara | Files touched by this commit (1)
Log message:
Packaged fine on DragonFly 3.2.2 + gcc47
   2013-02-04 12:03:55 by Makoto Fujiwara | Files touched by this commit (3)
Log message:
Packaged fine on DragonFly 3.2.2 + gcc47
   2013-02-02 06:55:07 by Makoto Fujiwara | Files touched by this commit (1)
Log message:
Add NetBSD/i386 5.2 seems OK and Dragonfly is not supported.
   2013-02-02 06:09:39 by Makoto Fujiwara | Files touched by this commit (1)
Log message:
Add comment for currently dropping old patches.
   2013-02-02 06:06:43 by Makoto Fujiwara | Files touched by this commit (8)
Log message:
Import gdb-7.5 as wip/gdb.

   The purpose of a debugger such as GDB is to allow 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.

Next | Query returned 35 messages, browsing 31 to 40 | previous