1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-22 14:12:10 +02:00
cdt/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_dbg.htm
Jeff Johnston 6acb6dbc70 Add CDT Standalone Debugger
- add org.eclipse.cdt.debug.application plugin which supports running
  CDT debugger as Eclipse application
- add org.eclipse.cdt.debug.application.docs plugin which is the
modified
  CDT docs
- add org.eclipse.cdt.debug.standalone-feature which bundles the
  two aforementioned plugins
- add org.eclipse.cdt.debug.standlone.source-feature

Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13
Reviewed-on: https://git.eclipse.org/r/25845
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2014-05-05 15:39:30 -04:00

46 lines
No EOL
2 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Debug overview</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Debug overview</h1>
<p>The debugger lets you see what's going on &quot;inside&quot; a program while it
executes.</p>
<p>In order to debug your application, you must use executables compiled for
debugging. These executables contain additional debug information that lets the
debugger make direct associations between the source code and the binaries
generated from that original source.</p>
<p>The Stand-alone debugger uses GDB as the underlying debug engine. It translates each
user interface action into a sequence of GDB commands and processes the output from GDB to
display the current state of the program being debugged. </p>
<p><strong>Tip:</strong> Editing the source after compiling causes the line numbering to be out of
step because the debug information is tied directly to the source. Similarly,
debugging optimized binaries can also cause unexpected jumps in the execution
trace.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_over_cdt.htm">Overview of the CDT</a><br>
<a href="cdt_c_dbg_info.htm">Debug information</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_o_debug.htm">Debugging</a><br>
&nbsp;</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_run_dbg_pages.htm">Run and Debug dialog box</a></p><p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" > </p>
</div>
</body>
</html>