Debugger and method for debugging computer programs across multiple programming languages

• US 20060064677A1
• Filed: 09/22/2004
• Published: 03/23/2006
• Est. Priority Date: 09/22/2004
• Status: Active Grant

• Current Assignee: Harmon.ie R&d Ltd. (Harmon.ie, Inc.)
• Original Assignee: Mainsoft
• Inventors: Alaluf, Eyal, Bickson, Maya
• Granted Patent: US 7,478,366 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A debugger and method for debugging computer programs across multiple programming languages are provided. The debugging is performed at a source level of a computer program written in any programming language supported by the .Net® platform, while the program is executed over a Java runtime environment. The debugger disclosed provides a call stack display and an expression evaluator. Furthermore, the debugger allows software developers to step through Java source code and follow the execution flow of the Java program. One exemplary embodiment of the disclosed debugger is an extension of the Microsoft® Visual Studio .Net®.

Claims

1. A debugger for debugging a computer program across multiple programming languages, wherein the debugging is performed on .Net®

platform source code of the computer program, while the computer program is executed within a Java runtime environment, the debugger comprising;

an integrated development environment (IDE) interface capable of interfacing with at least one IDE tool for the purpose of receiving a plurality of debugging commands, each having at least one parameter;

a debug engine capable of determining a current breakpoint location in said source code;

a Java debugger interface (JDI) capable of communicating with at least one Java debugger;

a convert engine capable of converting said parameters of each of said debugging commands from a .Net®

compliant format to a Java compliant format, said convert engine being further capable of converting said debugging commands from said Java compliant format in Java source code to said .Net®

compliant format;

an expression evaluator capable of at least parsing said parameters; and

a debug information repository at least comprising debug information,

wherein said convert engine implements at least a conversion algorithm designed to bridge the semantic differences between .Net®

programming languages and Java programming language and wherein the debugging is performed at a source level of the computer program written in any programming language supported by the .Net platform.

2. The debugger of claim 1, wherein said .Net®

source code is written using at least one of the following programming languages;

C++ with managed extensions;

C-sharp (C#);

Visual Basic;

Pascal; and

COBOL.

3. The debugger of claim 1, wherein said Java runtime environment comprises at least one of:

a Java virtual machine (JVM); and

a Java 2 platform enterprise edition (J2EE) server.

4. The debugger of claim 1, wherein said IDE tool is at least the Microsoft Visual Studio®

for .Net®

.

5. The debugger of claim 1, wherein each of said plurality of debugging commands is at least one of:

a breakpoint command;

an execution command;

an evaluation command; and

a stack frame information command.

6. The debugger of claim 5, wherein the command parameters of said evaluation command comprise at least a .Net®

expression.

7. The debugger of claim 6, wherein said .Net®

expression is at least one of;

an identifier;

a literal;

an operator;

a function call; and

a variable.

8. The debugger of claim 6, wherein said expression evaluator is further capable of generating a tree representation of said parsed .Net®

expression.

9. The debugger of claim 8, wherein said tree representation comprises at least one atomic element of said parsed .Net®

expression.

10. The debugger of claim 9, wherein said atomic element is at least of one of an operator;

and an operand.

11. The debugger or claim 9, wherein the data type of each of said atom elements is determined using said debug information.

12. The debugger of claim 9, wherein each of said atomic elements is converted to said Java compliant format by means of said convert engine.

13. The debugger of claim 12, wherein said convert engine further constructs a Java expression from said atomic elements converted to Java.

14. The debugger of claim 13, wherein said Java expression is sent to said Java debugger for evaluation.

15. The debugger of claim 14, wherein said evaluation results are returned to said IDE tool.

16. The debugger of claim 15, wherein said evaluation results are displayed in at least one expression window of the Microsoft Visual Studio®

for .Net®

.

17. The debugger of claim 16, wherein said expression window comprises at least one of:

Watch;

Locals;

This/Me; and

Autos.

18. The debugger of claim 5, wherein said execution command comprises at least one of:

stepping into a code line in the Java source code; and

moving to a next code line in said Java source code.

19. The debugger of claim 18, wherein the code line to stop at is determined by said convert engine.

20. The debugger of claim 5, wherein said stack frame information command comprises displaying stack frame information generated by said Java debugger over said IDE tool.

21. The debugger of claim 20, wherein displaying said stack frame information further comprises the step of translating said stack frame information generated, by said Java debugger to said .Net®

compliant format. 11189112.01

22. The debugger of claim 20, wherein said stack frame information comprises at least one of:

a class name;

a function name;

a list of arguments;

the type of each of said arguments; and

the value of each of said arguments.

23. The debugger of claim 1, wherein said debug information is extracted from at least one of:

program database (PDB) files;

dynamically linked library (DLL) files; and

extensible markup language (XML) files.

24. The debugger of claim 2, wherein said expression evaluator comprises a plurality of parsers, wherein each of said parsers is designed to parse one of the .Net®

programming languages.

25. A method for debugging a computer program across multiple programming languages, wherein the debugging is performed on .Net®

platform source code of the computer program, while the computer program is executing within a Java runtime environment, said method comprising;

providing an integrated development environment (IDE) interface capable of interfacing with at least one IDE tool for the purpose of receiving a plurality of debugging commands, each having at least one parameter;

providing a debug engine capable of determining a current breakpoint location in the source code;

providing a Java debugger interface (JDI) capable of communicating with at least one Java debugger;

providing a convert engine capable of converting said parameters of each of said debugging commands from a .Net®

compliant format to a Java compliant format, said convert engine being further capable of converting said debugging commands from said Java compliant format in Java source code to said .Net®

compliant format;

providing an expression evaluator capable of at least parsing said parameters; and

,

providing a debug information repository at least comprising debug information,

receiving a debugging command in a .Net®

compliant format from an integrated development environment (IDE) tool;

converting the parameters of said plurality of debugging commands from said .Net®

compliant format to Java compliant format;

performing said debugging command with the converted parameters using a Java debugger and a Java runtime environment;

converting the debugging results returned by said Java debugger from said Java source code to .Net®

source code; and

, returning the converted debugging results to said IDE tool, wherein the debugging is performed at a source level of the computer program written in any programming language supported by the .Net®

platform.

26. The method of claim 25, wherein said computer program comprises a Net source code written using at least one of the following programming languages:

C++with managed extensions;

C-sharp (C#);

Visual Basic;

Pascal; and

COBOL.

27. The method of claim 25, wherein said Java runtime environment comprises at least one of:

a Java virtual machine (JVM); and

a Java 2 platform enterprise edition (J2EE) server.

28. The method of claim 25, wherein said IDE tool is at least the Microsoft Visual Studio®

for .Net®

.

29. The method of claim 25, wherein said debugging command is at least one of:

a breakpoint command;

execution command;

an evaluation command; and

a stack frame information command.

30. The method of claim 29, wherein the command parameters of said evaluation command comprise at least a .Net®

expression.

31. The method of claim 30, wherein said .Net®

expression is at least one of;

an identifier;

a literal;

an operator;

a function call; and

a variable.

32. The method of claim 29, wherein said breakpoint command comprises setting and converting of at least one of the following parameters:

a line breakpoint;

a function breakpoint; and

a conditional breakpoint.

33. The method of claim 32, wherein converting the parameters of said breakpoint command is followed by translating a .Net®

location of a breakpoint to a Java location.

34. The method of claim 33, wherein said .Net®

location is determined using at least;

a .Net®

file name;

a line number; and

a column number.

35. The method of claim 33, wherein said Java location is determined using at least:

a Java class name;

a line number; and

a Java offset.

36. The method of claim 33, wherein said Java location is returned to said IDE tool.

37. The method of claim 30, wherein the step of converting said parameters of said plurality of debugging commands further comprises:

parsing said .Net®

expression to determine at least one atomic element of said .Net expression;

constructing a tree representation from said atomic elements of said .Net®

expression;

determining the data type of each of said atomic elements of said .Net®

expression;

transforming each of said atomic elements of said .Net®

expression to said Java compliant format; and

,

constructing a Java expression from said atomic elements of said .Net®

expression.

38. The method of claim 37, wherein the step of performing said debugging command comprises evaluating said Java expression to provide debugging evaluation results.

39. The method of claim 38, wherein said debugging results are said evaluation results returned by said Java debugger.

40. The method of claim 39, wherein said evaluation results are displayed by said IDE tool.

41. The method of claim 40, wherein said evaluation results are displayed in at least one expression window of the Microsoft Visual Studio®

for .Net®

.

42. The method of claim 41, wherein said expression window comprises at least one of:

Watch;

Locals;

This/Me; and

Autos.

43. The method of claim 37, wherein said at least one atomic element is at least of one of:

an operator; and

an operand.

44. The method of claim 37, wherein the data type of each of said atomic elements is determined using debug information.

45. The method of claim 34, wherein said breakpoint command comprises setting of at least one of the following breakpoints:

a line breakpoint, a function breakpoint, and a conditional breakpoint.

46. The method of claim 35, wherein the step of performing said debugging command further comprises setting a breakpoint at said Java location in said Java source code.

47. The method of claim 46, wherein said debugging results comprise said Java location.

48. The method of claim 46, wherein said execution command comprises at least one of:

stepping into a code line in said Java source code; and

moving to a next code line in said Java source code.

49. The method of claim 48, wherein the step of performing said debugging command further comprises:

determining a next break location in said Java source code; and

checking if said Java debugger can stop at said next break location, and if so said Java debugger breaks at said next break location;

otherwise, repeating said determining a next break location step.

50. The method of claim 49, wherein the step of converting said debugging results further comprises translating said Java break location to a .Net location.

51. The method of claim 50, wherein said .Net®

location is determined using at least;

.Net file name;

line number; and

column number.

52. The method of claim 48, wherein the step of performing said debugging command comprises generating said stack frame information by said Java debugger.

53. The method of claim 52, wherein the step of converting said debugging results further comprises translating said stack frame information generated by said Java debugger to .Net®

compliant format.

54. The method of claim 53, wherein the .Net®

compliant format of said stack frame information is displayed in said IDE tool.

55. The method of claim 52, wherein said stack frame information comprises at least one of:

class name;

function name;

list of arguments;

the type of each of said argument; and

the value of each of argument.

56. A computer program product method, including computer-readable media with instructions to enable a computer to implement a process for debugging a computer program across multiple programming languages, wherein the debugging is performed on .Net®

platform source code of the computer program, while the computer program is executing within a Java runtime environment, said method comprising;

providing an integrated development environment (IDE) interface capable of interfacing with at least one IDE tool for the purpose of receiving a plurality of debugging commands, each having at least one parameter;

providing a debug engine capable of determining a current breakpoint location in the source code;

providing a Java debugger interface (JDI) capable of communicating with at least one Java debugger;

providing a convert engine capable of converting said parameters of each of said debugging commands from a .Net®

compliant format to a Java compliant format, said convert engine being further capable of converting said debugging commands from said Java compliant format in Java source code to said .Net®

compliant format;

providing an expression evaluator capable of at least parsing said parameters;

providing a debug information repository at least comprising debug information;

receiving a debugging command in a .Net®

compliant format from an integrated development environment (IDE) tool;

converting the parameters of said plurality of debugging commands from said .Net®

compliant format to Java compliant format;

performing said debugging command with the converted parameters using a Java debugger and a Java runtime environment;

converting the debugging results returned by said Java debugger from said Java source code to .Net®

source code; and

returning the converted debugging results to said IDE tool,

wherein the debugging is performed at a source level of the computer program written in any programming language supported by the .Net®

platform.

57. The computer program product of claim 56, wherein said computer program comprises a .Net®

source code written using at least one of the following programming languages;

C++ with managed extensions;

C-sharp (C#);

Visual Basic;

Pascal; and

COBOL.

58. The computer program product of claim 56, wherein said Java runtime environment comprises at least one of:

a Java virtual machine (JVM); and

Java 2 platform enterprise edition (J2EE) server.

59. The computer program product of claim 56, wherein said IDE tool is at least the Microsoft Visual Studio for .Net®

.

60. The computer program product of claim 56, wherein said debugging command is at least one of:

a breakpoint command;

an execution command;

an evaluation command; and

a stack frame information command.

61. The computer program product of claim 60, wherein the command parameters of said evaluation command comprise at least a .Net®

expression.

62. The computer program product of claim 60, wherein said .Net®

expression is at least one of;

an identifier;

a literal;

an operator;

a function call; and

a variable.

63. The computer program product of claim 61, wherein the step of converting said parameters of said plurality of debugging command further comprises:

parsing said .Net®

expression to determine at least one atomic element of said .Net expression;

constructing a tree representation from said atomic elements of said .Net®

expression;

determining the data type of each of said atomic elements of said .Net®

expression;

transforming each of said atomic elements of said .Net®

expression to said Java compliant format; and

,

constructing a Java expression from said atomic elements of said .Net®

expression.

64. The computer program product of claim 63, wherein the step of performing said debugging command further comprises evaluating said Java expression.

65. The computer program product of claim 64, wherein said debugging results are evaluation results returned by said Java debugger.

66. The computer program product of claim 65, wherein said evaluation results are displayed in said IDE tool.

67. The computer program product of claim 66, wherein said evaluation results are displayed in at least one expression window of the Microsoft Visual Studio®

for .Net®

.

68. The computer program product of claim 67, wherein said expression window comprises at least one of:

Watch;

Locals;

This/Me; and

Autos.

69. The computer program product of claim 63, wherein each of said atomic elements is at least of one of:

an operator; and

an operand.

70. The computer program product of claim 63, wherein the data type of each of said atomic elements is determined using debug information.

71. The computer program product of claim 60, wherein said breakpoint command comprises setting at least one of the following breakpoints:

a line breakpoint;

a function breakpoint; and

a conditional breakpoint.

72. The computer program product of claim 71, wherein the command parameters comprise a .Net®

location of a breakpoint.

73. The computer program product of claim 72, wherein said .Net®

location is determined using at least;

a .Net®

file name;

a line number; and

a column number.

74. The computer program product of claim 72, wherein the step of converting said parameters of said plurality of debugging command further comprises translating said .Net®

location of a breakpoint to a Java location.

75. The computer program product of claim 74, wherein said Java location is determined using at least:

a Java class name;

a line number; and

a Java offset.

76. The computer program product of claim 75, wherein the step of performing said debugging command further comprises setting a breakpoint at said Java location in the Java source code.

77. The computer program product of claim 74, wherein said debugging results comprise said Java location.

78. The computer program product of claim 76, wherein said execution command comprises at least one of:

stepping into a code line in the Java source code; and

moving to a next code line in the Java source code.

79. The computer program product of claim 78, wherein the step of performing said debugging command further comprises:

determining a next break location in the Java source code; and

checking if said Java debugger can stop at said next break location, and if so said Java debugger breaks at said next break location;

otherwise, repeating said determining a next break location step.

80. The computer program product of claim 79, wherein the step of converting said debugging results further comprises translating said Java break location to a .Net®

location.

81. The computer program product of claim 80, wherein said .Net®

location is determined using at least;

a .Net®

file name;

a line number; and

a column number.

82. The computer program product of claim 80, wherein the step of performing said debugging command further comprises generating said stack frame information by said Java debugger.

83. The computer program product of claim 82, wherein the step of converting said debugging results further comprises translating said stack frame information generated by said Java debugger to said .Net®

compliant format.

84. The computer program product of claim 83, wherein the .Net®

compliant format of said stack frame information is displayed in said IDE tool.

85. The computer program product of claim 82, wherein said stack frame information comprises at least one of:

a class name;

a function name;

a list of arguments;

the type of each of said arguments; and

the value of each of said arguments.

86. A method for evaluating an expression when debugging a computer program across multiple programming languages, wherein the debugging is performed on .Net®

source code of the computer program, while the computer program is executing within a Java runtime environment, said method comprising;

providing an integrated development environment (IDE) interface capable of interfacing with at least one IDE tool for the purpose of receiving a plurality of debugging commands, each having at least one parameter;

providing a debug engine capable of determining a current breakpoint location in the source code;

providing a Java debugger interface (JDI) capable of communicating with at least one Java debugger;

providing a convert engine capable of converting said parameters of each of said debugging commands from a .Net®

compliant format to a Java compliant format, said convert engine being further capable of converting said debugging commands from said Java compliant format in Java source code to said .Net®

compliant format;

providing an expression evaluator capable of at least parsing said parameters; and

,

providing a debug information repository at least comprising debug information,

receiving at least a .Net®

expression to be evaluated from an integrated development environment (IDE) tool;

determining a current break location in a .Net®

source code;

parsing said .Net®

expression into at least one atomic element;

generating a tree representation from said atomic elements;

determining the data type of each of said at least one atomic elements;

traversing said tree representation for the purpose of determining the data type of said .Net®

expression;

converting each atomic element to a format compliant with said at least one Java debugger;

constructing a Java expression from said atomic elements converted to a Java compliant format; and

,

evaluating said Java expression using said at least one Java debugger and a Java runtime environment to provide evaluation results.

87. The method of claim 86, further comprising:

returning said evaluation results to said IDE tool; and

displaying said evaluation results in said IDE tool.

88. The method of claim 86, wherein said .Net®

source code is written using at least one of the following programming languages;

C++ with managed extensions;

C-sharp (C#);

Visual Basic;

Pascal; and

COBOL.

89. The method of claim 86, wherein said IDE tool is at least the Microsoft Visual Studio®

for. .Net®

.

90. The method of claim 86, wherein said evaluation results are displayed in at least one expression window of said Microsoft Visual Studio®

for .Net®

.

91. The method of claim 90, wherein said expression window comprises at least one of:

Watch;

Locals;

This/Me; and

Autos.

92. The method of claim 86, wherein said at least one atomic element is at least of one of:

an operator; and

an operand.

93. The method of claim 86, wherein the data type of each of said atomic elements is determined using debug information.

94. The method of claim 86, wherein said .Net®

expression comprises at least one of;

an identifier;

a literal;

an operator;

a function call; and

a variable.

95. A computer program product method, including computer-readable media with instructions to enable a computer to implement a process for evaluating at least an expression when debugging a computer program across multiple programming languages, wherein the debugging is performed on .Net®

source code of the computer program, while the computer program is executing within a Java runtime environment, said method comprising;

providing an integrated development environment (IDE) interface capable of interfacing with at least one IDE tool for the purpose of receiving a plurality of debugging commands, each having at least one parameter;

providing a debug engine capable of determining a current breakpoint location in the source code;

providing a Java debugger interface (JDI) capable of communicating with at least one Java debugger;

providing a convert engine capable of converting said parameters of each of said debugging commands from a .Net®

compliant format to a Java compliant format, said convert engine being further capable of converting said debugging commands from said Java compliant format in Java source code to said .Net®

compliant format;

providing an expression evaluator capable of at least parsing said parameters;

providing a debug information repository at least comprising debug information;

receiving from an integrated development environment (IDE) tool at least a .Net®

expression to be evaluated;

determining current break location in the .Net®

source code;

parsing said .Net®

expression into atomic elements;

generating a tree representation from said atomic elements;

determining the data type of each of said atomic elements;

traversing said tree representation for the purpose of determining the data type of said .Net®

expression;

converting each of said atomic elements to a format compliant with a Java debugger;

constructing a Java expression from said converted atomic elements to a Java compliant format; and

evaluating said Java expression using a Java debugger and a Java runtime environment to provide evaluation results.

96. The computer program product of claim 95, further comprising:

returning said evaluation results to said IDE tool; and

displaying said evaluation results in said IDE tool.

97. The computer program product of claim 95, wherein said .Net®

source code is written using at least one of the following programming languages;

C++ with managed extensions;

C-sharp (C#);

Visual Basic;

Pascal; and

COBOL.

98. The computer program product of claim 95, wherein said IDE tool is at least the Microsoft Visual Studio for .Net®

.

99. The computer program product of claim 95, wherein said evaluation results are displayed in at least one expression window of said Microsoft Visual Studio®

for .Net®

.

100. The computer program product of claim 95, wherein said expression window comprises at least one of:

Watch;

Locals;

This/Me; and

Autos.

101. The computer program product of claim 95, wherein said atomic elements comprise at least of one of:

an operator; and

an operand.

102. The computer program product of claim 95, wherein the data type of each of said atoms is determined using debug information.

103. The computer program product of claim 95, wherein said .Net®

expression comprises at least one of;

an identifier;

a literal;

an operator;

a function call; and

a variable.