| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
The src.conf(5) manpage is to follow in a few days.
Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
|
| |
|
|
|
|
|
|
| |
mode when in non-UTF-8 multibyte locales (e.g. EUC, GB2312, etc.).
PR: 91909
|
|
|
|
| |
- Reduce trivial code duplications.
|
| |
|
|
|
|
|
| |
2. Add command 'thread signal' to print out current thread's signal mask
and pending signals.
|
|
|
|
| |
Approved by: kan
|
| |
|
|
|
|
|
|
|
|
| |
mode. This allows one to use kgdb on /dev/mem and be able to patch memory
on a live system. This is identical to what -wcore used to do in previous
gdb versions for FreeBSD.
Requested by: wpaul
|
|
|
|
|
|
|
|
|
| |
similar the the Solaris implementation. Repackage the krb5 GSS mechanism
as a plugin library for the new implementation. This also includes a
comprehensive set of manpages for the GSS-API functions with text mostly
taken from the RFC.
Reviewed by: Love Hörnquist Åstrand <lha@it.su.se>, ru (build system), des (openssh parts)
|
|
|
|
|
| |
PR: docs/88848
Prodded by: remko
|
|
|
|
| |
Reviewed by: nyan
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Jimmie James <jimmiejaz@gmail.com>
PR: docs/88427
|
|
|
|
| |
easier to keep them in sync.
|
| |
|
|
|
|
|
| |
PR: bin/87964
Submitted by: Frank Mayhar frank at exit dot com
|
|
|
|
|
| |
PR: 87969
Obtained from: Fedora (Tim Waugh)
|
|
|
|
|
| |
PR: 35333
Submitted by: Hendrik Scholz <hendrik@scholz.net>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
shipped with GNU cpio 2.6 fails to test for it.
|
|
|
|
| |
apparently fails to do it.
|
| |
|
| |
|
|
|
|
| |
already available.
|
|
|
|
| |
they are not visible from wchar.h.
|
|
|
|
|
|
|
| |
think that's the lot, but it's hard to understand the exception code
by mere glancing at it.
MFC after: 1 week
|
|
|
|
|
|
|
| |
stack by claiming the frame when the IP is 0. It's a bit of a kluge,
but avoids screens full of bogus frames.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
syscall. This is an entry from userland anyway.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
just needs to be taught about all the other entry points and the
unwinder needs to be taught about the frame variation between them.
MFC after: 1 week
|
|
|
|
|
|
|
| |
just needs to be taught about all the other entry points and the
unwinder needs to be taught about the frame variation between them.
MFC after: 1 week
|
|
|
|
|
|
|
| |
just needs to be taught about all the other entry points and the
unwinder needs to be taught about the frame variation between them.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
list of frame sniffers so that trapframes can be detected. The kluge
is needed because this version of gdb only supports appending a
sniffer to the list of sniffers and the moment kgdb gets a chance to
add its own frame sniffer, the target's default frame sniffer is
already in the list. Since the default frame sniffer claims any
frame thrown at it, kgdb's frame sniffer never gets to smell (a
process much akin to tasting, but with lesser chance of hurling :-)
This commit adds dummy frame sniffers that never claim a frame and
as such don't fix anything yet. However, we now have frame sniffers
and they are being called, so it's just a matter of adding meat to
the bones and we'll be able to properly unwind across trapframes.
MFC after: 1 week
|
|
|
|
|
| |
Triggered by: Stijn Hoop <stijn@win.tue.nl>
on freebsd-questions
|
|
|
|
|
|
|
| |
PR: docs/84485
Submitted by: garys
Approved by: keramida
MFC after: 3 days
|
| |
|
|
|
|
| |
I think this is the last one which needs it.)
|
|
|
|
|
|
|
|
| |
this library build repeatably. (This change was made to libstdc++
several months ago; I just realized today that it would help here as
well.)
Approved by: kan
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
command does, but worse.
o Remove the obscure proc command, because it does what the thread
command does, but not unambigously.
o Move the PID to the extra thread info, where it makes sense and
where it doesn't confuse users. The extra thread info holds some
process information, to which the PID belongs.
o Implement the to_find_new_threads target method by having it call
the target beneath us if we're not using KVM. This makes sure that
new threads are found when using the remote target.
o Fix various core dump scenarios:
- Implement the to_files_info target method. Previously the
'info target' command would cause a NULL pointer dereference.
- Don't assume there's a current thread. We're not initialized
in all cases. This prevents a NULL pointer dereference.
- When we're not ussing KVM, have the to_xfer_memory target
method call the target beneath us. This avoids calling into
KVM with a NULL pointer.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
static.
o Register a function with atexit(3) to close the KVM object if
we have one open.
o Show the unread portion of the kernel's message buffer before
presenting the prompt. It's bound to provide some useful info.
o Don't call kgdb_target() twice. It results in having all threads
listed twice.
MFC after: 1 week
|