|This is the talk page for discussing improvements to the GNU Debugger article.|
|WikiProject Computing||(Rated Start-class)|
|WikiProject Free Software / Software / Computing||(Rated Start-class, Low-importance)|
I tried, but there was no way to find out which languages are supported. I guess someone has to look this up in the code.
Having a look in the documentation helps... http://sourceware.org/gdb/current/onlinedocs/gdb/Summary.html#Summary and more specifically, a section called "Supported Languages": http://sourceware.org/gdb/current/onlinedocs/gdb/Supported-Languages.html#Supported-Languages 18.104.22.168 (talk) 12:06, 28 November 2011 (UTC)
I changed the insight link to point to the redhat resource rather than to a disambiguity page which then points to redhat resource. Someone changed it back to ambiguous page which isn't helpful in my opinion. Daniel.Cardenas 18:46, 11 May 2006 (UTC)
- The Insight reference should be a red link, since it's articleworthy. Stan 00:14, 12 May 2006 (UTC)
- It has it's own article: libbfd. Since GDB relies heavily on this, it should be explained in the article, but I don't think I know enough to do this myself. Gronky 13:24, 1 March 2007 (UTC)
With kgdb, kernel developers can debug a kernel much like they can application programs.
I think there is a syntax mistake in this sentence but english is not my mother thong so I don't know how to make it right.
- Claimed fixed. VanishingUser 05:59, 24 April 2007 (UTC)
In the sentence "As of version 7.0, "reversible debugging" support — allowing a debugging session to step backwards, much like rewinding a crashed program to see what happened — and Python scripting support have been added." have is gramatically correct because of the 'and' (Reversible debugging support AND Python scripting support HAVE been added. NOT "Reversible debugging support AND python scripting support HAS been added.") The information given about the debugging support is extra information and does not change the singularity/plurality of the sentence. Please refrain from changing this back to 'has'. Gabe G23 (talk) 17:00, 18 December 2009 (UTC)
Merge from GNU Debugger front-end
I'm proposing to merge since there isn't that many out there and it's repeating part of the Limitations section. --Witchinghour 12:56, 9 June 2007 (UTC)
- Opposed, at least until someone checks Special:Whatlinkshere/GNU_Debugger_front-end in detail and gives an analysis of how this merge affects the linked-from articles. Lentower 17:10, 9 June 2007 (UTC)
- Comment, so everybody would be in the know, here's what happend. GNU Debugger front-end was Debugger front-end and it had a list of applications claiming to be debugger front-ends. I had the proposal to merge it with the Debugger article instead. I went thru that list and was removing spam and other crap. Finally what it came down to was a list of GNU Debugger/DBX front-ends. So I moved the page to it's new title. Removed the merge request from Debugger to GNU Debugger. And that's how we're here right now. I also removed insight from the list since it's more like a graphical fork of GDB rather than an seperate front end i.e. insight can't exist without the GDB source code. --Witchinghour 18:30, 9 June 2007 (UTC)
- Support. I can't think of much more to say about debugger (GDB or otherwise) frontends in general than a sentence or two, so insufficient for its own article, and this article ought to mention GDB's frontends and link to articles for each notable one. Stan 20:18, 9 June 2007 (UTC)
Example session section – broken reference
The example program that this section refers to has been removed from the article Stack Trace. I don't know the correct protocol for resolving this problem, but I wanted to bring it to the attention of someone who does. – Dazmax 21:47, 1 December 2007 (UTC)
Where does that ISBN number come from? I can't find any relation between both 22.214.171.124 (talk) 12:40, 28 November 2011 (UTC) You can find it in the PDF version only, see: http://sourceware.org/gdb/download/onlinedocs/gdb.pdf.gz — Preceding unsigned comment added by 126.96.36.199 (talk) 14:19, 30 November 2011 (UTC)
Examples of commands and example session
GDB Should be Classified as a Machine Code Monitor
I'm always curious of my old Commodore 64 computer's internal operatings, and I further recently found insight of how Jim Butterfield (ie. Jim Butterfield 1936-2007 Wikipedia) created Supermon/Supermon64 machine language monitor that many Commodore assembly language programmers used to debug and test code. Further research shows the program performs extremely similar to GDB, of setting breakpoints within memory!
Basically within the first paragraph of the GDB Wikipedia, GDB should be further classified as a "Machine Code Monitor" Wikipedia. Readers can then further research the Machine Language Monitor Wikipedia and further understand how GDB (or a debugger) works by using a computer's memory contents and real time assembly language in order to set breakpoints, or perform other tasks!
This is likely very important to understand; as without this information is very similar to trying to program good efficient source code without knowing anything about a lower level Assembly Language or C/C++ language, when scripting. Without knowing how a CPU processes bits and bytes (via Assembly Language), somebody writing a C program or a higher level scripting language program, may very well write computer source code that does not effectively utilize the computer's (ie. CPU) resources wisely or efficiently!
Some points of reference: 1) Richard Stallman seems to have referenced the TRS-80 computer TBUG debugger, another common machine language monitor, within his "Debugging with GDB: The GNU Source-level Debugger" book.
2) Atmel makes reference to GDB as a Machine Language Monitor here; The Atmel AVR is a RISC microcontroller from Atmel, in which it's debugger is referenced as, "avrmon-stk200 – avr- gdb compatible GNU/Linux-based debug monitorA machine code monitor (aka machine language monitor) is software built-into or separately available for various computers, allowing the user to enter commands to view and change the memory of the machine, with options to load and save memory contents fro system for connecting to Atmel's STK200 Starter Kit"
A machine code monitor is synonymous with Machine Language Monitor. (ie Machine Code Monitor Wikipedia)
- Short answer: no. Longer answer: Yes, GDB does have machine-code-level abilities, but they are incidental to its main purpose as a source-level debugger, and without the right low-level stub on the target, GDB is not going to have full access to the target hardware, as one would expect with a monitor. Stan (talk) 18:53, 20 March 2014 (UTC)