Talk:Debugger

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Software / Computing   
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 

linkfarm[edit]

I'm fixin' to remove the "Notable debuggers" section completely, and replace it with a link to Category:Debuggers, which is more complete, doesn't have linkspam, and so on. Anyone object? -- Mikeblas 02:10, 27 March 2007 (UTC)

agreed: the really few, historic debuggers (GDB, dbx debugger, etc.) can be in the "See also list".
I think that remedy should be added to this list because it was the first multithreaded visualization debugger and

over the next few years it will be the primary interface style that all debuggers go to for debugging large multicore systems, gpus etc. Remedy Debugger May 29, 2008 Peterkimrowe (talk) 23:34, 29 May 2008 (UTC)

the "Remarkable debuggers" section includes tools that have no debugging in their own spec, like Daedalus.
--Hgfernan 14:41, 17 June 2007 (UTC)


good plan... —Preceding unsigned comment added by 80.47.53.138 (talk) 06:23, 17 June 2009 (UTC)

Where to mention debugging formats ?[edit]

which do you think is the best place to mension debugging formats like DWARF and stabs ? here or in debugging ?

--Hgfernan 14:35, 17 June 2007 (UTC)

Proposal to rewrite Debugger article[edit]

I propose a major rewrite of the Debugger article. Although I find nothing factually wrong with it, and it includes many important points, I feel that it does not read clearly for someone who doesn't already understand what a debugger is, nor does it mention the most essential points up front. A preliminary outline of my proposed rewrite is as follows:

Introduction: A debugger is a computer program which is used as a tool by a programmer to view and control the internal workings of another program at a very detailed level. This second program is said to be running under (the) debugger.

View & control: Controlling execution (single-step, suspend/resume); examining variables during suspension; breakpoints, crashes, exceptions.

Purposes of using a debugger: The term "debugger" is somewhat of a misnomer, in that a debugger does not itself debug code. Although a debugger can be of great assistance to a programmer in debugging code, a debugger is equally useful for analyzing and understanding the operation of an existing program, without any intention of diagnosing bugs. This understanding can be used to document the program, or to modify it. A debugger is a particularly important tool for hackers.

source-level debuggers vs machine-language debugger

ISS

program behavior may differ when running under a debugger (execution speed, timing issues, different compile options)

If there is general agreement to rewrite this article somewhat along these lines, I'll definitely want lots of help from previous contributors. (By the way, this is my very first attempt to contribute to Wikipedia, so please let me know if I've violated protocol.)

Bill Rubin 21:21, 21 August 2007 (UTC)

Agreed wholeheartedly; I'd also like to see coverage of:
OS Interfaces
ie, ptrace, procfs, Win32, hardware-level, simulation, etc
Engines
hardware debug registers, how a software breakpoint works
Symbolic Debugging
How opcode-level debugging tools interface with source languages
High Level Languages
Quick overview of how Java and C# provide debugger interfaces
Advanced Techniques
User mode single stepping, hit tracing, detours, hooking

--- tqbf 19:33, 5 November 2007 (UTC)

Kim Rowe 21:21, 17 April 2009 (UTC)

This is a totally simplistic view from the point of view of source code only debugging. Rethink this in terms of trying to solve the problem of debugging a system and the feature set changes completely. I'd also like to see coverage of:
OS Interfaces
Multiple processes and multiple threads
Display of debugging information using a variety of techniques
High level models for debugging
Simulation and debugging —Preceding unsigned comment added by Peterkimrowe (talkcontribs) 17:53, 17 April 2009 (UTC)

Proposed merge from Debugger front-end[edit]

As the Debugger front-end article is a subtopic of Debugger, and the articles are not particularly long, I have proposed a merge. --Snigbrook (talk) 21:01, 30 August 2008 (UTC)


Who knows - the entire debugger section has the wrong slant as far as I'm concerned. It misses what debuggers are intended to do. ... - April 2009 —Preceding unsigned comment added by Peterkimrowe (talkcontribs) 17:54, 17 April 2009 (UTC)


Saved/rescued external links[edit]

I start to save/rescue external links that are added to this article per Nov-26-2010 in this section, so that they are not lost , but also do not further pollute the article. I'm considering to move relevant links to the Open Directory Project.

  • see link added here [1]
  • see link added here [2]

Ptrb (talk) 14:29, 27 November 2010 (UTC)

Lacks a history section[edit]

A history section with notable early implementations (and related languages) would be nice. 76.10.128.192 (talk) 03:21, 20 September 2012 (UTC)