Work around MinGW mangling of "host:/path"
[msysgit/historical-msysgit.git] / mingw / info / gdb / Remote.html
blob5390f72c8894772bff394bc2c6f477044248b754
1 <html lang="en">
2 <head>
3 <title>Debugging with GDB</title>
4 <meta http-equiv="Content-Type" content="text/html">
5 <meta name="description" content="Debugging with GDB">
6 <meta name="generator" content="makeinfo 4.3">
7 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
8 </head>
9 <body>
10 <div class="node">
11 <p>
12 Node:<a name="Remote">Remote</a>,
13 Next:<a rel="next" accesskey="n" href="KOD.html#KOD">KOD</a>,
14 Previous:<a rel="previous" accesskey="p" href="Byte-Order.html#Byte%20Order">Byte Order</a>,
15 Up:<a rel="up" accesskey="u" href="Targets.html#Targets">Targets</a>
16 <hr><br>
17 </div>
19 <h3 class="section">Remote debugging</h3>
21 <p>If you are trying to debug a program running on a machine that cannot run
22 GDB in the usual way, it is often useful to use remote debugging.
23 For example, you might use remote debugging on an operating system kernel,
24 or on a small system which does not have a general purpose operating system
25 powerful enough to run a full-featured debugger.
27 <p>Some configurations of GDB have special serial or TCP/IP interfaces
28 to make this work with particular debugging targets. In addition,
29 GDB comes with a generic serial protocol (specific to GDB,
30 but not specific to any particular target system) which you can use if you
31 write the remote stubs--the code that runs on the remote system to
32 communicate with GDB.
34 <p>Other remote targets may be available in your
35 configuration of GDB; use <code>help target</code> to list them.
37 </body></html>