Talk:GNU Debugger

message: 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
92.195.40.38 (talk) 12:06, 28 November 2011 (UTC)
thread_title: Supported language

message: 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)
replies: text: The Insight reference should be a red link, since it's articleworthy. Stan 00:14, 12 May 2006 (UTC)
thread_title: Where should insight link point?

message: Should libbfd be described in this article or in Binutils? Gronky 13:16, 1 March 2007 (UTC)
replies: text: 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)
thread_title:  Libbfd 

message: 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)
thread_title:  syntax 

message: I removed VAX from the lower list, because it already was in the top. --Ysangkok 16:25, 9 May 2007 (UTC)
thread_title:  Features section 

message: 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)
replies: text: 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)

text: 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)

text: 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)
thread_title:  Merge from [[GNU Debugger front-end]] 

message: Where does that ISBN number come from? I can't find any relation between both 92.195.40.38 (talk) 12:40, 28 November 2011 (UTC)
thread_title:  Documentation ISBN 

message: Doesn't this violate WP:NOTMANUAL?  — Preceding unsigned comment added by Krofna (talk • contribs) 13:46, 7 May 2013 (UTC)
thread_title:  Examples of commands and example session 

message: 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)
Interesting! --roger (talk) 18:36, 20 March 2014 (UTC)
replies: text: 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)
thread_title:  GDB Should be Classified as a Machine Code Monitor 

message: Hello fellow Wikipedians,
I have just modified one external link on GNU Debugger. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20100829051021/http://kldp.net:80/projects/mygdb/ to http://kldp.net/projects/mygdb
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 22:10, 6 January 2017 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 3 external links on GNU Debugger. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Corrected formatting/usage for http://kldp.net/projects/mygdb/
*Added archive https://web.archive.org/web/20141022045312/https://developer.palm.com/content/api/dev-guide/pdk/eclipse-gdb-debugging.html to https://developer.palm.com/content/api/dev-guide/pdk/eclipse-gdb-debugging.html
*Added archive https://web.archive.org/web/20070303045900/http://sourceware.org/gdb/current/onlinedocs/gdbint.html to http://sourceware.org/gdb/current/onlinedocs/gdbint.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 16:18, 9 October 2017 (UTC)
thread_title:  External links modified