summaryrefslogtreecommitdiffstats
path: root/gnu/usr.bin/gdb
Commit message (Collapse)AuthorAgeFilesLines
* Unbreak - remove leftover reference to pcb_rflags.peter2005-09-281-1/+0
|
* Claim frames corresponding to tl(0|1)_intr and tl0_trap as well. Imarcel2005-09-111-1/+4
| | | | | | | think that's the lot, but it's hard to understand the exception code by mere glancing at it. MFC after: 1 week
* Unwind across intrframes as well. While here, better handle bottom ofmarcel2005-09-111-2/+8
| | | | | | | 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
* Unwind across intrframes as well.marcel2005-09-111-3/+8
| | | | MFC after: 1 week
* Unwind across trap frames. Handles all entry points, except the EPCmarcel2005-09-111-47/+201
| | | | | | syscall. This is an entry from userland anyway. MFC after: 1 week
* Unwind across trapframes. All kernel entries are handled.marcel2005-09-101-11/+94
| | | | MFC after: 1 week
* Unwind across trap frames. This adds most of the meat. The sniffermarcel2005-09-101-1/+93
| | | | | | | 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
* Unwind across trap frames. This adds most of the meat. The sniffermarcel2005-09-101-10/+95
| | | | | | | 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
* Unwind across trap frames. This adds most of the meat. The sniffermarcel2005-09-101-6/+86
| | | | | | | 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
* Add a kluge to allow kgdb(1) to inject its own frame sniffer in themarcel2005-09-1011-13/+188
| | | | | | | | | | | | | | | | | 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
* Fix backtraces. Supply registers from the register window.marcel2005-08-161-16/+7
| | | | MFC after: 3 days
* o Remove the obscure tid command, because it does what the threadmarcel2005-08-061-100/+41
| | | | | | | | | | | | | | | | | | | | | | | 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
* o As mentioned in the previous commit: make the KVM error buffermarcel2005-08-061-6/+58
| | | | | | | | | | | | 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
* Spell "currently" correctly.keramida2005-07-281-1/+1
|
* kvm_openfiles() uses the supplied buffer for storing error messagespeter2005-06-241-1/+0
| | | | | | | | | 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
* Add support for XMM registers in GDB for x86 processors that supportdfr2005-05-312-12/+112
| | | | | | | SSE (or its successors). Reviewed by: marcel, davidxu MFC After: 2 weeks
* Don't try to enable event reporting for core file, it is not writable.davidxu2005-05-061-0/+2
|
* Report events from thread library.davidxu2005-04-121-16/+210
|
* Print thread address.davidxu2005-04-051-4/+4
| | | | PR: threads/76821
* Implement and document the -q and -f options with their correspondingmarcel2005-03-022-6/+46
| | | | | | | long form (-quiet and -fullname resp.) Bump documentation date. PR: bin/78031 MFC after: 5 days
* .It the -v option.obrien2005-03-011-1/+1
|
* Restore r1.2 change to use TARGET_ARCH.kan2005-02-201-1/+1
| | | | Submitted by: kris
* Attempt to make kgdb little more useful and easy to use. Properly initializekan2005-02-2010-25/+218
| | | | | | | | 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.
* Remove mention of the -k and -wcore options because they don'tmarcel2005-02-151-14/+0
| | | | | | | | exist anymore. PR: doc/70943 Submitted by: Jun <junsu at delphij dot net> Reviewed by: delphij
* Use the system gnuregex library vs. building GNU regex bits into libibertyobrien2005-02-144-6/+11
| | | | | | | and using them. Reviewed by: marcel,imp Desired by: ache
* Markup nits.ru2005-01-131-4/+3
|
* When grabbing registers for an lwp, fake the inferior's pid using thepeadar2005-01-111-2/+6
| | | | | | | | | | | | | 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
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-212-2/+2
| | | | OK'ed by: core
* Source changes to allow building a cross-debugger. Move solib.c andmarcel2004-12-0516-5/+29
| | | | | | | | 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.
* Fix previous commit. GDB_CROSS_DEBUGGER needs to be defined for allmarcel2004-12-052-9/+5
| | | | subdirectories.
* Makefile (only) changes to allow building a cross debugger.marcel2004-11-3010-21/+50
|
* s/MACHINE_ARCH/TARGET_ARCH/. We use TARGET_ARCH to pick the MD filesmarcel2004-11-301-1/+1
| | | | for libgdb and should do so here as well.
* [Sorry, forgot to commit my source changes in my previous commit.]joerg2004-11-221-2/+5
| | | | | | | | | | | | | | 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.
* Document all options and general usage.joerg2004-11-221-0/+67
| | | | | | | | | | | | 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.
* Fix the abuse of Ar macros for designating flag options, use Fl instead.joerg2004-11-221-4/+4
|
* Always set current thread when activating thread debugger,davidxu2004-11-151-1/+1
| | | | | the current thread may already be added by fbsd_find_new_threads, this can result that current thread is not set correctly.
* Whitespace fix.marcel2004-11-091-1/+1
|
* Prepare for a subsequent import: If the first letter of the filenamemarcel2004-11-091-35/+43
| | | | | | | | | | | 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.
* For variables that are only checked with defined(), don't provideru2004-10-242-2/+2
| | | | any fake value.
* Update to readline 5.0ache2004-10-181-3/+7
|
* If the argument to the -r flag starts with a ':' or a '|', don't try tobrooks2004-09-031-1/+1
| | | | | | | | | 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
* Only compile fbsd-thread.c on amd64 and i386, other architecturesdavidxu2004-08-221-1/+5
| | | | have not been tested yet.
* Fix comments, most are style fix.davidxu2004-08-221-21/+11
|
* Fix some text messages.davidxu2004-08-221-2/+2
|
* Add code to support statically linked binary and .core file of threadeddavidxu2004-08-221-177/+367
| | | | program.
* Improve the usage. Without any arguments, kgdb(1) works on /dev/memmarcel2004-08-152-49/+126
| | | | | | | | | 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.
* Initialize thread_db module.davidxu2004-08-101-0/+2
|
* Initialize thread_db module.davidxu2004-08-081-0/+2
|
* 1. Add some code check if thread suspending or resuming is failed.davidxu2004-08-082-4/+80
| | | | 2. Add code to retrieve thread tls address.
* Hook kgdb into the build.marcel2004-07-251-1/+1
|
OpenPOWER on IntegriCloud