| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
not --line-bufferring.
PR: docs/72985
Submitted by: John Engelhart <johne@zang.com>
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
changes, start on a new line. Insertion of a filename will keep the
diff limited to the block of filenames that have the same first letter
instead of creating a huge diff. While here, move remote.c after the
remote-*.c files and move tui.c after the tui-*.c files. This matches
the order of ls(1) and makes it easier to compare object files created
by a stock gdb(1) build with the list of files we have here.
This is a non-functional change only.
|
|
|
|
| |
Pointed out by: ru
|
| |
|
|
|
|
|
|
| |
GCC 3.4.2 work unintentioanlly.
Reminded by: bms
|
|
|
|
| |
any fake value.
|
| |
|
| |
|
| |
|
|
|
|
| |
It expand functions scope too wide
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
/lib/{libm,libreadline}
/usr/lib/{libhistory,libopie,libpcap}
in preparation for doing the same thing to RELENG_5. HUGE amounts of
help for determining what to bump provided by kris.
Discussed on: freebsd-current
Approved by: re (not required for commit but something like this should be)
|
|
|
|
|
|
| |
well, but I'll let Marcel decide whether he wants to build a .so or not.
Without this, building certain ports that use objc have fatal errors.
|
|
|
|
| |
script substitution markers.
|
|
|
|
|
|
|
| |
that parse it.
PR: 72139
Submitted by: Eugene M. Kim <gene@nttmcl.com>
|
| |
|
|
|
|
| |
need for hack workarounds in tools/lib32/build32.sh.
|
|
|
|
|
|
|
| |
interrupted.
MT5: 7 days
MT4: 7 days
|
|
|
|
|
| |
non-intrusive way. This should also fix the PowerPC build that
broke due to this change.
|
|
|
|
| |
trying to build the .o's.
|
|
|
|
|
|
|
|
|
| |
make sure it is a device. GDB special cases these prefixes and treats
:#### as a tcp port on localhost and executes what ever follows '|'.
This allows kgdb to debug via dconschat.
Discussed with: marcel
|
| |
|
|
|
|
| |
have not been tested yet.
|
| |
|
| |
|
|
|
|
| |
program.
|
|
|
|
| |
FreeBSD 4.11-RELEASE.
|
|
|
|
|
|
|
|
|
| |
in rev. 1.57. Fix this regression by making cc_tools a new-style
build-tool in Makefile.inc1. For details of what has been fixed,
please see the gnu/usr.bin/cc/cc_tools/Makefile,v 1.52 commit log.
Caught this by accidentally touching param.h while in the process
of cross-buildworld for amd64.
|
|
|
|
|
|
|
|
|
| |
with the currently running kernel image. Otherwise, one of -c, -n or
-r is expected for working on a particular core file (-c), working
on a saved dump (-n) or working remotely (-r). When working on a
saved dump, a kernel may be omitted.
For a remote debugging session (-r), kgdb(1) will use the specified
device.
|
|
|
|
| |
block profiling.
|
|
|
|
|
|
|
|
|
|
|
|
| |
input files:
1999-06-25 Paul Eggert <eggert@twinsun.com>
* inflate.c (huft_build):
Set n to length of v, to detect improper tables.
Don't accidentally grow j past z.
MFC after: 3 days
|
|
|
|
|
|
| |
of them in several places.
Noticed by: bsdimp
|
|
|
|
| |
from the original.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
2. Add code to retrieve thread tls address.
|
|
|
|
|
|
|
|
|
|
| |
of releases. The -DNOCRYPT build option still exists for anyone who
really wants to build non-cryptographic binaries, but the "crypto"
release distribution is now part of "base", and anyone installing from a
release will get cryptographic binaries.
Approved by: re (scottl), markm
Discussed on: freebsd-current, in late April 2004
|
|
|
|
|
|
|
|
| |
gets most of it content back now, when symbols from LIB2FUNCS are actually
compiled.
Noticed by: Steve Kargl <gk at troutmask dot apl dot washington dot edu>
Pointy hat to: kan
|
|
|
|
| |
OK'ed by: kan
|
|
|
|
|
|
| |
it is only used by build tools.
Submitted by: grehan
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is basicly a shell on top of libgdb that knows about kernel threads,
kernel modules and kvm(3). As the word "beginnings" implies, not
all of the features have been implemented yet. The tool is useful
and I'd like feedback on the taken route.
The simplest way to debug a kernel core file is:
kgdb -n 0
This opens /var/crash/vmcore.0 with the corresponding kernel in
the object directory (kernel.debug is used if it exists).
Typical things that need to be added are:
o Auto loading of kernel modules,
o Handling of trapframes so that backtraces can be taken across
them,
o Some fancy commands to extract useful information out of a core
file,
o Various (probably many) other things.
|