XML export from and import into a debugger

• US 20080155506A1
• Filed: 12/21/2006
• Published: 06/26/2008
• Est. Priority Date: 12/21/2006
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Boskovic, Srdjan
• Application Number:
  US11/644,173
• Publication Number:
  US 20080155506A1
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 11/3648 using additional hardware

Abstract

A system includes a debugger in a processor-based system. The processor-based system further includes a module to serialize data associated with the debugger into an XML format. The system also includes a module to export the serialized data out of the debugger.

Claims

1. A method comprising:

providing a debugger for a first processor-based system;

serializing data associated with the debugger into an XML format; and

exporting the serialized data out of the debugger.

2. The method of claim 1, wherein the data is compared with other XML data using a module including one or more of an XML parser and an XML change detection algorithm.

3. The method of claim 1, wherein the serialized data from the debugger in the first processor-based system is exported to a debugger associated with a second processor-based system.

4. The method of claim 3, wherein the first processor-based system is that of a customer and the second processor-based system is that of a software provider.

5. The method of claim 3, wherein the second processor-based system is substantially similar to the first processor-based system.

6. The method of claim 3, wherein the second processor-based system includes one or more of the first processor-based system and a processor-based system separate from the first processor-based system.

7. The method of claim 6, further comprising:

deserializing the data from the first processor-based system; and

executing the second processor-based system using the deserialized data from the first processor-based system.

8. The method of claim 7, wherein the execution of the second processor-based system using the deserialized data from the first processor-based system includes one or more of setting breakpoints in the debugger associated with the second processor-based system, locating an error in one or more of the first processor-based system and the second processor-based system, diagnosing one or more of the first processor-based system and the second processor-based system, and preparing test data.

9. The method of claim 6, further comprising providing a user interface, the user interface having access to a plurality of XML-formatted data files, so that a user can select an XML-formatted file to import into one or more of the debugger of the first processor-based system and the debugger of the second processor-based system.

10. The method of claim 9, wherein the user interface provides a form in which a user may enter XML formatted data for import into one or more of the debugger of the first processor-based system and the debugger of the second processor-based system.

11. The method of claim 1, wherein the data associated with the debugger includes source code generated by a source code generator.

12. A method comprising:

providing a debugger and a source code generator for a first processor-based system;

using the source code generator to generate source code and data structures as a function of data associated with the debugger; and

exporting the source code and data structures out of the debugger of the first processor-based system.

13. The method of claim 12, wherein the source code and data structures are exported to a second processor-based system.

14. The method of claim 13, wherein the second processor-based system includes one or more of the first processor-based system and a processor-based system separate from the first processor-based system.

15. The method of claim 14, wherein the first processor-based system is substantially similar to the second processor-based system.

16. The method of claim 13, wherein the first processor-based system is that of a customer and the second processor-based system is that of a software provider.

17. The method of claim 14, further comprising:

copying one or more of the source code and data structures into a module in the second processor based system; and

using the module in the second processor-based system in a unit test on the second processor-based system.

18. A system comprising:

a debugger in a first processor-based system;

a module to serialize data associated with the debugger into an XML format; and

a module to export the serialized data out of the debugger.

19. The system of claim 18, further comprising:

a debugger associated with a second processor-based system, the debugger associated with the second processor-based system configured to import data exported by the debugger in the first processor-based system;

a module to deserialize the data from the first processor-based system; and

a module to execute the second processor-based system using the deserialized data from the first processor-based system;

wherein the second processor-based system includes one or more of the first processor-based system and a processor-based system separate from the first processor-based system.

20. The system of claim 19, further comprising:

a user interface, the user interface having access to a plurality of XML-formatted data files, so that a user can select an XML-formatted file to import into the debugger of the first processor-based system or the debugger of the second processor-based system;

wherein the user interface provides a form in which a user may enter XML formatted data for import into the debugger of one or more of the first processor-based system and the debugger of the second processor-based system.

21. A system comprising:

a debugger and a source code generator associated with a first processor-based system, the source code generator generating source code and data structures as a function of data associated with the debugger; and

a module to export the source code and data structures out of the debugger of the first processor-based system.

22. The system of claim 21, further comprising:

a debugger associated with a second processor-based system, the debugger associated with the second processor-based system importing the source code from the first processor-based system;

a module to copy one or more of the source code and data structures into program code in the second processor based system; and

a module to use the program code in the second processor-based system in a unit test on the second processor-based system;

wherein the second processor-based system includes one or more of the first processor-based system and a processor-based system separate from the first processor-based system.

23. A method comprising:

halting an execution of a computer-based process with a debugger;

importing XML data into the debugger;

serializing data associated with the debugger into an XML format;

comparing the imported XML data and the serialized debugger data; and

continuing execution of the process.

24. A system comprising:

a debugger;

a module to import XML data into the debugger;

a module to serialize data associated with the debugger into an XML format; and

a module to compare the XML data and the serialized debugger data.