| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
in future calls, so we can't free it here. The right place to free the
buffer would be to be after kvm_close(), but we don't do that yet. A
static buffer would work too.
Reviewed by: marcel (who has other plans for this anyway)
Approved by: re
|
|
|
|
|
|
|
| |
SSE (or its successors).
Reviewed by: marcel, davidxu
MFC After: 2 weeks
|
| |
|
| |
|
|
|
|
| |
PR: threads/76821
|
|
|
|
|
|
|
| |
long form (-quiet and -fullname resp.) Bump documentation date.
PR: bin/78031
MFC after: 5 days
|
| |
|
|
|
|
| |
Submitted by: kris
|
|
|
|
|
|
|
|
| |
it to recognise what ABI to use on amd64 (and possibly others) platform.
Display PID and process name as a part of the 'info threads' output, TIDs
alone are too confusing. Introduce new commmands 'tid <tid>' and 'proc <pid>'
to accompany gdb's default 'thread <thread num>' to make the task of switching
between different contexts easier.
|
|
|
|
|
|
|
|
| |
exist anymore.
PR: doc/70943
Submitted by: Jun <junsu at delphij dot net>
Reviewed by: delphij
|
|
|
|
|
|
|
| |
and using them.
Reviewed by: marcel,imp
Desired by: ache
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lwp ID before invoking the underlying target operation.
For corefiles, we rely on gdb internals to do this, and it uses the
pid as an index, rather than the lwpid, so previously, backtraces
for multithreaded core files wasn't working correctly. For processes,
we currently use ptrace directly, so fixup that code to also use
the pid directly.
Discussed With: marcel, davidxu
MFC After: 4 days
|
|
|
|
| |
OK'ed by: core
|
|
|
|
|
|
|
|
| |
solib-svr4.c to the MD makefiles because they are native files for
alpha and sparc64, but target files for amd64, i386 and ia64.
Note that kgdb(1) does not yet build as a cross-debugger due to
libkvm.
|
|
|
|
| |
subdirectories.
|
| |
|
|
|
|
| |
for libgdb and should do so here as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document all options and general usage.
Implement the -a option to bump the annotation_level. This improves
the Emacs gud behaviour. You can now supply the following function
(defun gud-gdb-massage-args (file args) (cons "-a" args))
(e.g. by evaluating it from the *scratch* buffer) and get the normal
jump to the source window when browsing the stack.
We should probably eventually supply our own kgdb submode to gud.el.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement the -a option to bump the annotation_level. This improves
the Emacs gud behaviour. You can now supply the following function
(defun gud-gdb-massage-args (file args) (cons "-a" args))
(e.g. by evaluating it from the *scratch* buffer) and get the normal
jump to the source window when browsing the stack.
We should probably eventually supply our own kgdb submode to gud.el.
|
| |
|
|
|
|
|
| |
the current thread may already be added by fbsd_find_new_threads,
this can result that current thread is not set correctly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
any fake value.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
2. Add code to retrieve thread tls address.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
functions. Only ps_p{read|write} remains.
o Remove ps_getpid. We don't need it now.
|
| |
|
|
|
|
|
|
| |
that have been added to <sys/procfs.h>. This change has no effect
because the source file that would be affected is not compiled on
FreeBSD. Hence, this is for completeness only.
|
| |
|
| |
|
|
|
|
| |
The file was repo copied into our doc directory.
|
|
|
|
| |
Fixed some style bugs.
|
|
|
|
|
|
|
| |
and sparc64.
Note that the debugger doesn't support threading, nor kernel
debugging yet.
|
|
|
|
| |
Submitted by: Szilveszter Adam <sziszi@bsd.hu>
|
| |
|
|
|
|
|
| |
rechecked by somebody who knows what is meant to happen here. The new
libreadline rluser.texinfo file duplicates the '@defcodeindex bt' entry.
|
| |
|
| |
|