History log of /dflybsd-src/test/debug/README (Results 1 – 6 of 6)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.4.3, v3.4.2, v3.4.1, v3.4.0, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1
# b2ec19dd 14-Dec-2004 Matthew Dillon <dillon@dragonflybsd.org>

Document vmpageinfo.c


# 5d71f24c 14-Oct-2004 Matthew Dillon <dillon@dragonflybsd.org>

*** empty log message ***


# 3a8683bb 06-Oct-2004 Matthew Dillon <dillon@dragonflybsd.org>

Update ncptrace.c to handle DragonFly_Stable and HEAD.
Add ttyinfo.c (does a sanity check on the kernel's clist data)


# 94669a32 26-Jun-2004 Hiten Pandya <hmp@dragonflybsd.org>

Add a debug directory under src/test, where we will house all of our debug
scripts that will aid the debugging of the kernel and other code.

I have added a GDB macro set in file 'gdb.kernel' which c

Add a debug directory under src/test, where we will house all of our debug
scripts that will aid the debugging of the kernel and other code.

I have added a GDB macro set in file 'gdb.kernel' which contains some
helpful macros, such as listing processes, iterating CPU's globaldata,
a kldstat(1) style macro etc.

The 'gdb.kernel' file was written by:

Hiten Pandya <hmp@backplane.com>,
Matthew Dillon <dillon@apollo.backplane.com>

The kldstat(1) macro should be helpful with the asf(1) utility which
is used for setting the right offset to load the KLD's symbols.

show more ...


# 1f8a7fec 22-Sep-2010 Sascha Wildner <saw@online.de>

Move test/debug/gdb.kernel to share/misc/gdbinit.

The main reason is that crashinfo(8) was previously searching for
this script in /usr/src because it wasn't installed in the system.

This led to tw

Move test/debug/gdb.kernel to share/misc/gdbinit.

The main reason is that crashinfo(8) was previously searching for
this script in /usr/src because it wasn't installed in the system.

This led to two little problems. First, if you didn't have source
in /usr/src, the core.xy.txt file wouldn't have all the information.
Second, if you had source in /usr/src but it was outdated and didn't
have all the commands that crashinfo(8) required, you would get
unwanted errors in core.xy.txt.

Therefore, put the file in share/misc from where it will get
installed and where other initialization files such as indent.pro
also reside. The user can then copy it to ~/.gdbinit as he likes.

show more ...