Linux Application Debugger

Table of Contents

• Introduction
  • LDB Limitations
  • LDB Interface
  • Using the LDB
• Commands Comparison
  • Entering and Exiting the Debugger
  • Debugger Commands
  • Running Programs
  • Stopping and Continuing
  • Examining the Stack
  • Examining Source Files
  • Examining Data
  • Using Languages
  • Examining the Symbol Table
  • Altering Execution
  • Debugger Files
  • Controlling Debugger
  • Canned Sequences of Commands
• LDB Sample Session
• Copyright Notice
• Disclaimer

Introduction

Commands Comparison

This section provides a comparative analysis of the LDB and GNU Debugger commands. The LDB commands are grouped by their functionality, similar to the way they are listed in GDB documentation, and divided into three color groups:

GDB commands supported by LDB

GDB commands partially supported by LDB

GDB commands not supported by LDB

Back to TOC

LDB Sample Session

This is a sample of the code generated by the Linux Application Debugger during the debugging session. User input is emphasized in this font.

$ ldb maincall
Linux Application Debugger, Version 6.0 Beta,Build 20020108.
Copyright (c) 2001-2002 Intel Corporation. All Rights Reserved.

(ldb) break main
Breakpoint 1 at 0x8048113: file maincall.c, line 15.
(ldb) run
Starting program: maincall

Breakpoint 1: file maincall.c line 15.
15      {
(ldb) list
10      extern int inc7(int, int);
11      extern int inc8(int, int);
12      extern int inc9(int, int);
13
14      main( int argc, char *argv[])
15      {
16          /* Test the call stack */
17          int a;
18          int b;
19          int c;
20
(ldb) next
21          switch(argc)
(ldb) next
25                        argv[0]);
(ldb) list
20
21          switch(argc)
22          {
23            case 1:
24                fprintf(stdout, "argv: %s\n",
25                        argv[0]);
26                break;
27            case 2:
28                fprintf(stdout, "argv: %s %s\n",
29                        argv[0],argv[1]);
30                break;
(ldb) break inc1
Breakpoint 2 at 0x80483a3: file inc1.c, line 4.
(ldb) continue
argv: maincall
Breakpoint 2: file inc1.c line 4.
4       {
(ldb) list
1       #include 
2
3       inc1( int a, int b )
4       {
5           /* Test the call stack */
6           int c;
7           c = inc2( ++a, ++b);
8           fprintf(stdout, "Result: %d  (inc1 original values a:%d b:%d)\n", c, a, b);
9           return(a+b);
(ldb) next
7           c = inc2( ++a, ++b);
(ldb) print a
$2 = 1
(ldb) print b
$3 = 1
(ldb) next
Result: 22  (inc9 original values a:10 b:10)
Result: 20  (inc8 original values a:9 b:9)
Result: 18  (inc7 original values a:8 b:8)
Result: 16  (inc6 original values a:7 b:7)
Result: 14  (inc5 original values a:6 b:6)
Result: 12  (inc4 original values a:5 b:5)
Result: 10  (inc3 original values a:4 b:4)
Result: 8  (inc2 original values a:3 b:3)
8           fprintf(stdout, "Result: %d  (inc1 original values a:%d b:%d)\n", c, a, b);
(ldb) print c
$4 = 6
(ldb) continue
Result: 6  (inc1 original values a:2 b:2)
Result: 4  (inc0 original values a:1 b:1)
Result: 2  (original values a:0 b:0)
(ldb) quit

$

Back to TOC

Copyright Notice

Copyright © 2001-2002 Intel Corporation. All rights reserved.

*Other names and brands may be claimed as the property of others.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and in other countries.

Back to TOC

Disclaimer

Information in this online help is provided in connection with Intel® products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel® products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications.

Intel may make changes to specifications and product descriptions at any time, without notice.

Designers must not rely on the absence or characteristic of any features or instructions marked "reserved" or "undefined" for processors. Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.

The processors referred to in this online help may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Back to TOC