Object-oriented symbolic debugger using a compiler driven database and state modeling to control program execution

• US 5,812,850 A
• Filed: 11/13/1995
• Issued: 09/22/1998
• Est. Priority Date: 11/13/1995
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Object Technology Licensing Corporation (Apple Inc.)
• Inventors: Wimble, Michael D.
• Primary Examiner(s): Voeltz, Emanuel Todd
• Assistant Examiner(s): CORCORAN, PETER JOSEPH
• Application Number:
  US08/557,993
• Time in Patent Office: 1,044 Days
• Field of Search: 395/701, 395/705, 395/709, 395/704, 395/183.13, 395/183.14
• US Class Current: 717/131
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler

Abstract

A human oriented object programming system provides an interactive and dynamic process for debugging computer programs which facilitates the development of complex computer programs such as operating systems and large applications with graphic user interfaces (GUIs). The debugging system uses a database of information relating machine executable code to source code. The database is developed during the compilation process using an extensible object-oriented set of tools. The tools standardize the information developed during compilation into an information format which the debugging system can utilize to provide the user with a powerful source code view of the corresponding executing code.

Claims

1. An apparatus for use on a computer system having an operating system thereon, the apparatus controlling an executable program having executable code lines created by processing source code lines with a compiler to generate object code modules and linking the object code modules with a linker, wherein the compiler and the linker generate debugging information during processing, the apparatus comprising:

(a) a database creator which is responsive to the debugging information for creating an information database containing a plurality of map entries defining particular relationships between the source code lines and the executable code lines and methods for accessing data variable locations;

(b) a plurality of software model objects modeling the executable program and the operating system, the software model objects containing data and code therein for generating state data concerning the state of the executable program and the operating system; and

(c) a debugger engine which is responsive to the state data generated by the plurality of software model objects for examining the information database to control the computer to selectively execute the executable program.

2. The apparatus of claim 1, wherein said information database comprises at least one instruction map comprising one or more instruction map entries for mapping at least one executable code line to one or more source code line selections.

3. The apparatus of claim 1, wherein said information database comprises instruction index range information for providing information regarding an range of source code lines associated with a map entry.

4. The apparatus of claim 1, wherein said information database comprises source reference information for providing information regarding source code lines associated with a map entry.

5. The apparatus of claim 4, wherein said source reference information comprises information defining source references in terms of portions of source code lines.

6. The apparatus of claim 1, wherein said information database comprises data optimization annotation for providing information regarding implications of code optimization.

7. The apparatus of claim 6, wherein said data optimization annotation indicates shared lifetime.

8. The apparatus of claim 6, wherein said data optimization annotation indicates constraint.

9. The apparatus of claim 6, wherein said data optimization annotation indicates inline expansion optimization.

10. The apparatus of claim 1, wherein said information database comprises code optimization annotation for providing information regarding implications of code optimization.

11. The apparatus of claim 1, wherein said information database comprises attribute information for providing information regarding source position.

12. The apparatus of claim 11, wherein said informat ion regarding source position comprises function information.

13. The apparatus of claim 11, wherein said information regarding source position comprises frame construction information.

14. The apparatus of claim 11, wherein said information regarding source position comprises characteristic location information.

15. The apparatus of claim 1, wherein the compiler and the linker comprise information providers and wherein the apparatus further comprises an adopt function for asking the database creator to adopt a format of information of an information provider.

16. The apparatus of claim 1, wherein said information database comprises at least one token map comprising one or more token map entries for mapping a token from token map entry to a source code line selection.

17. The apparatus of claim 1, wherein said information database comprises at least one source reference for defining a source of a token.

18. The apparatus of claim 1, wherein said information database comprises at least one kind indicator for defining a kind of a token.

19. The apparatus of claim 1, wherein said information database comprises at least one data indicator for defining an entry into a type map which defines a type of token.

20. The apparatus of claim 1, wherein said information database comprises at least one data indicator for defining an entry into a data map entry associated with a token.

21. The apparatus of claim 1, wherein said information database comprises at least one statement map comprising one or more statement map entries for mapping source code lines to a hierarchy of semantic statement elements.

22. The apparatus of claim 1, wherein said information database comprises at least one source reference for defining a source of a statement element.

23. The apparatus of claim 1, wherein said information database comprises at least one kind indicator for defining a kind of a statement element.

24. The apparatus of claim 1, wherein said information database comprises at least one parent indicator for defining a parent of a statement element.

25. The apparatus of claim 1, wherein said information database comprises at least one breakpoint indicator for defining one or more breakpoints related to a statement element.

26. The apparatus of claim 1, wherein said information database comprises at least one data map comprising data map entries for mapping data variable locations to one or more source code lines.

27. The apparatus of claim 1, wherein said information database comprises at least one variable indicator for defining a variable in one of the source code lines.

28. The apparatus of claim 1, wherein said information database comprises at least one source reference for defining a source of a data object defined by an associated map entry.

29. The apparatus of claim 28, wherein said source reference comprises at least one range of characters.

30. Th e apparatus of claim 28, wherein said source reference comprises at least one set of character ranges.

31. The apparatus of claim 28, wherein said source reference comprises at least one reference to a token in a token map.

32. The apparatus of claim 28, wherein said source reference comprises at least one set of tokens.

33. The apparatus of claim 28, wherein said source reference comprises at least one range of entries in a token map.

34. The apparatus of claim 1, wherein said information database comprises at least one live location reference for defining a formula which, when used in a context of an executing program, specifies a data location of a data object defined by an associated map entry.

35. The apparatus of claim 34, wherein said live location reference comprises an absolute address.

36. The apparatus of claim 34, wherein said live location reference comprises a program component reference.

37. The apparatus of claim 34, wherein said live location reference comprises a register reference.

38. The apparatus of claim 1, wherein said information database comprises at least one accessing formula defining a value at an address associated with a map entry.

39. The apparatus of claim 38, wherein said accessing formula comprises at least one read accessing formula for defining how to read a value associated with a map entry.

40. The apparatus of claim 38, wherein said accessing formula comprises at least one write accessing formula for defining how to create a value associated with a map entry.

41. The apparatus of claim 38, wherein said accessing formula comprises information defining a value at an address.

42. The apparatus of claim 38, wherein said accessing formula comprises information defining a variable embedded in value at location specified.

43. The apparatus of claim 38, wherein said accessing formula comprises information defining an operator applied to left and right access formula to create new access formula.

44. The apparatus of claim 38, wherein said accessing formula comprises information defining an operator applied to access formula to create new access formula.

45. The apparatus of claim 38, wherein said accessing formula comprises information defining an address of a unary operator which is applied to access formula to derive a value which is a variable.

46. The apparatus of claim 38, wherein said accessing formula is implied by either a token map entry or an address of a variable.

47. The apparatus of claim 38, wherein said accessing formula comprises a reference to a self-defining literal value.

48. The apparatus of claim 42, wherein said accessing formula comprises a reference to a value directly located at an address.

49. The apparatus of claim 42, wherein said accessing formula comprises a formula describing a condition wherein a value contained in a location in such a way that the value is too complex to describe how to extract the value.

50. The apparatus of claim 1 wherein the information database comprises instruction maps containing instruction map entries defining particular relationships between the source code lines and the executable code lines and data maps containing data map entries having methods therein for accessing data variable locations.

51. The apparatus of claim 50 wherein the instruction map entries comprise a plurality of software code objects, the software code objects having data and software code therein for identifying selected source code lines.

52. The apparatus of claim 1 wherein the data map entries comprise a plurality of software code objects, the software code objects having data and software code therein for locating selected data variables.

53. The apparatus of claim 1 wherein the software model objects include a software model object for modeling the state of the executable program.

54. The apparatus of claim 1 wherein the software model objects include a software model object for modeling an instruction set used in the computer and operating system services used by the executable program.

55. A method for use on a computer system having an operating system thereon, the method controlling an executable program having executable code lines created by processing source code lines with a compiler to generate object code modules and linking the object code modules with a linker, wherein the compiler and the linker generate debugging information during processing, the method comprising the steps of:

(a) using the debugging information to create an information database containing a plurality of map entries defining particular relationships between the source code lines and the executable code lines and methods for accessing data variable locations;

(b) constructing a plurality of software model objects to model the executable program and the operating system, the software model objects containing data and code therein for generating state data concerning the state of the executable program and the operating system; and

(c) using the state data generated by the plurality of software model objects and information extracted from the information database to control the computer to selectively execute the executable program.

56. The method of claim 55 wherein step (a) comprises the steps of:

(a1) creating instruction maps containing instruction map entries defining particular relationships between the source code lines and the executable code lines and data maps containing data map entries having methods therein for accessing data variable locations.

57. The method of claim 56 wherein step (a1) comprises the step of:

(a1a) creating instruction map entries comprising a plurality of software code objects, the software code objects having data and software code therein for identifying selected source code lines.

58. The method of claim 56 wherein step (a1) comprises the step of:

(a1b) creating data map entries comprising a plurality of software code objects, the software code objects having data and software code therein for locating selected data variables.

59. The method of claim 55 wherein step (b) comprises the step of:

(b1) creating a software model object for modeling the state of the executable program.

60. The method of claim 55 wherein step (b) comprises the step of:

(b2) creating a software model object for modeling an instruction set used in the computer and operating system services used by the executable program.

61. A computer program product for use on a computer system having a memory and an operating system, the computer program product controlling an executable program having executable code lines created by processing source code lines with a compiler to generate object code modules and linking the object code modules with a linker, wherein the compiler and the linker generate debugging information during processing, the computer program product comprising a computer usable medium having computer readable program code thereon including:

(a) program code which uses the debugging information to create in the memory an information database containing a plurality of map entries defining particular relationships between the source code lines and the executable code lines and methods for accessing data variable locations;

(b) program code for constructing in the memory a plurality of software model objects to model the executable program and the operating system, the software model objects containing data and code therein for generating state data concerning the state of the executable program and the operating system; and

(c) program code loadable into the memory which uses the state data generated by the plurality of software model objects and information extracted from the information database to control the computer to selectively execute the executable program.

62. The computer program product of claim 61 wherein the program code which creates the information database creates in the memory instruction maps containing instruction map entries defining particular relationships between the source code lines and the executable code lines and further creates data maps containing data map entries having methods therein for accessing data variable locations.

63. The computer program product of claim 62 wherein the program which creates the instruction map entries creates in the memory a plurality of software code objects, the software code objects having data and software code therein for identifying selected source code lines.

64. The computer program product of claim 62 wherein the program which creates the data map entries creates in the memory a plurality of software code objects, the software code objects having data and software code therein for locating selected data variables.

65. The computer program product of claim 61 wherein the program code which creates the software model objects creates a software model object for modeling the state of the executable program.

66. The computer program product of claim 61 wherein the program code which creates the software model objects creates a software model object for modeling an instruction set used in the computer and operating system services used by the executable program.