WO1999034290A1 - Debugging system - Google Patents

Debugging system Download PDF

Info

Publication number
WO1999034290A1
WO1999034290A1 PCT/US1998/026874 US9826874W WO9934290A1 WO 1999034290 A1 WO1999034290 A1 WO 1999034290A1 US 9826874 W US9826874 W US 9826874W WO 9934290 A1 WO9934290 A1 WO 9934290A1
Authority
WO
WIPO (PCT)
Prior art keywords
debugging
debug
console
debugging function
providers
Prior art date
Application number
PCT/US1998/026874
Other languages
French (fr)
Inventor
Christopher James Koath
Original Assignee
Alcatel Usa Sourcing, L.P.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alcatel Usa Sourcing, L.P. filed Critical Alcatel Usa Sourcing, L.P.
Priority to AU19250/99A priority Critical patent/AU1925099A/en
Publication of WO1999034290A1 publication Critical patent/WO1999034290A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3664—Environments for testing or debugging software

Definitions

  • This invention relates to system debugging software. Developers write system debugging software to detect system hardware and software problems. Debugger software retrieves and displays information about the state of a system (e.g. hardware register values) and enables a developer to set the system to a specified state. Since systems include different hardware and software elements, developers often write dedicated debugger software from scratch for different systems and individual system elements.
  • state of a system e.g. hardware register values
  • a telecommunications terminal such as the LitespanTM- 2000 Access Network Unit made by DSCTM Communications Corp.
  • a telecommunications terminal connects subscriber lines, such as POTS (Plain Old Telephone Service) and ISDN (Integrated Services Digital Network) lines, to telecommunications exchanges and other telecommunications equipment.
  • subscriber lines such as POTS (Plain Old Telephone Service) and ISDN (Integrated Services Digital Network) lines
  • POTS Packet Old Telephone Service
  • ISDN Integrated Services Digital Network
  • a method of debugging a system includes maintaining a list of debugging function providers, receiving input from a console, and routing the console input to one of the debugging function providers.
  • Embodiments of the method may include the following features.
  • the method may also include receiving information from debugging function providers for console display.
  • the debugging function providers can be implemented in object-oriented software.
  • the method may be used to debug a telecommunications terminal.
  • the debugging function providers may request addition to the list of debugging function providers.
  • the list may be displayed on a console for operator selection.
  • the debugger function providers may supply a list of debugging functions or submenus.
  • the debugging functions may access both hardware and software system elements.
  • a method of debugging a system includes sending information from debugging function providers to a set of main debugging routines for display on a console.
  • a system for debugging includes a console, one or more debugging function providers, and a set of main debugging routines that maintain a list of debugging function providers and carry information between the console and the debugging function providers.
  • Embodiments of the system for debugging may include the following features.
  • the set of main debug routines and debugging function providers may communicate using a client/server message system.
  • the set of main debug routines and debugging function providers may both reside on a single card such as an X2M card.
  • a method of developing debug tools for debugging respective hardware and software elements under control of a user interaction with a console includes providing a common debug task that controls the console to provide a user interface that enables the user to interact with other debug objects and maintains a common programming interface for interaction with all of the debug objects, and generating debug objects for the respective system elements, each of the debug objects providing debug functions for the respective elements and functions that interact with the common debug task via the common programming interface.
  • the main debug task along with a set of console functions provide common console input/output (I/O) support for all debug objects. This reduces the amount of programming needed to create a debug object and thus reduces the development time needed to write new debugger software.
  • the main debug task also provides a menu of debug objects to allow a console operator to switch between different debug objects during a debugging session. This enables the console operator to see the interaction between the different system elements as they are being debugged.
  • Fig. 1 is a diagram of a console connected to hardware.
  • Fig. 2 is a diagram of a console, a main debug task, and a list of debug objects.
  • Fig. 3 is a diagram of a menu hierarchy.
  • Fig. 4 is a debugging session flowchart.
  • a console 10 is connected to a system 12.
  • a developer uses the console 10 to view and change the state of the connected system 12.
  • the system shown is a LitespanTM-120 telecommunications terminal 12 made by DSCTM Communications Corp.
  • the terminal 12 provides slots that accept different hardware cards (United States Serial No. 08/970,183 filed November 14, 1997, entitled "Telecommunications Terrninar describes a telecommunications terminal that accepts different hardware cards.
  • the terminal 12 connects each inserted card to other inserted cards via a bus (not shown).
  • the different cards include different components and perform different functions.
  • a Bandwidth Allocator, Processor, and Transmission (BPT) card 14 performs terminal management functions in addition to multiplexing and demultiplexing telecommunications signals.
  • a Channel Unit (CU) card 16 handles subscriber line signals. Many cards, including CU 16 and BPT 14, contain processors.
  • An X2M card (a card capable of serving several El channels and running N5.1 protocol software) possesses strong processing capability.
  • the debugging system includes object-oriented software instructions for console functions 19, a main debug task 18, and debug objects 20 and 22.
  • the console functions 19 include routines that handle I/O for a variety of consoles (e.g. dedicated serial or ethernet).
  • the main debug task 18 serves as an intermediary for passing information and commands between the console functions 10 and the debug objects 20 and 22 that provide debugging functions.
  • Each debug object 20 and 22 derives from a common base class (CDebug) that includes predefined characteristics. Derivation from a common base class speeds debug object 20 and 22 development. Each debug object 20 and 22 can be further programmed to perform specialized debugging functions with respect to associated hardware and software elements 24, 26. For example, one debug object 20 might access hardware registers on a POTS CU card, another debug object 22 might access memory on an ISDN CU card. Yet another debug object (not shown) might access information from software running on the system (e.g. queues, event flags, and history logs).
  • CDebug common base class
  • Each debug object 20 and 22 can be further programmed to perform specialized debugging functions with respect to associated hardware and software elements 24, 26. For example, one debug object 20 might access hardware registers on a POTS CU card, another debug object 22 might access memory on an ISDN CU card. Yet another debug object (not shown) might access information from software running on the system (e.g. queues, event
  • each debug object 20 and 22 includes a PrintMenu function 26 and a HandleNewInput function 28.
  • the PrintMenu function 26 produces menu information that allows the console operator to control debug objects 20 and 22.
  • the PrintMenu function 26 sends this menu information to the main debug task 18 for processing with other menu information to generate menus that are displayed on the console 10.
  • the HandleNewInput function 28 handles console 10 input routed to the debug object 20 by the main debug task 18. For example, based on console operator input, the main debug task 18 might send to a debug object's HandleNewInput function 28 a message to execute the debug object's 20 third menu choice (not shown).
  • the HandleNewInput function 30 calls the function corresponding to the menu choice.
  • Each debug object 20 and 22 also includes a Constructor 24 that, upon instantiation, sends a request to the main debug task to add the debug object 20 to a main debug task list 34 of debug objects.
  • the main debug task 18 includes a list 34 of pointers to debug objects, a router 32, and a PrintTopMenu function 36.
  • the router 32 sends information from the console functions 19 to debug objects 20 and 22.
  • the router 32 also receives information produced by the debug objects 20 and 22 and sends this information to the console functions 19 for display.
  • the router 32 and console functions 19 eliminate the need to rewrite console I/O functions or calls when developing a new debug object.
  • the PrintTopMenu function 36 produces a menu on the console that includes a list of debug objects.
  • the console operator can use this menu to switch among the different debug objects throughout a debugging session. This offers the console operator the convenience of debugging different system elements in a single session and the ability to debug the system as a whole as different system elements interact.
  • the main debug task PrintTopMenu function 36 and debug object PrintMenu functions 26 and 31 allow the console operator to navigate through different menus that include lists of the different debug objects and the debugging functions they provide.
  • the main debug task maintains a menu level variable 71 that indicates which menu should be displayed.
  • the main debug task displays its own menu 37, which includes a list of debug objects.
  • the console operator chooses one of the listed debug objects (e.g. Debug Object A) the menu level is incremented to level 1.
  • a debug object's PrintMenu function 26 could, for example, produce debug object menus 70 and 72.
  • the PrintMenu function 26 could send any one of these menus to the main debug task for console display.
  • a debug object menu 70 and 72 may include selections for debugging functions the object provides, selections for submenus, and a selection to return to a preceding menu.
  • the PrintMenu function 26 uses the menu level variable to determine which menu to produce.
  • the PrintMenu function adjusts the menu level variable based on console operator input to let the console operator navigate through debug object menus and submenus.
  • the main debug task sets the menu level at zero (step 39) indicating the main debug task should display its menu of debug objects (step 40).
  • the console operator selects one of the debug objects (step 42) causing the main debug task to increment the menu level variable (step 44) and route further console input to the chosen debug object's HandleNewInput function.
  • a debug object's HandleNewInput function processes information sent by the console via the main debug task. If the console operator chooses a debugging function provided by a debug object (step 50), the HandleNewInput function calls the corresponding debug object function (52) and then reproduces the debug object menu at the current menu level for further console operator selection (step 46). If the console operator chooses a debug object submenu (step 54), the menu level variable is incremented (step 58) and the debug object PrintMenu function produces the submenu for display on the console (step 46). If the console operator chooses to return to the preceding menu, the main debug task decrements the menu level variable (step 56).
  • the main debug task displays its own top level menu of debug objects (step 40) and ceases forwarding console input to the previously selected debug object. If the menu level variable is not zero after decrementing (step 60), the debug object's PrintMenu function produces the preceding debug object menu (step 46).
  • each CU card processor could contain its own hardware debug object and communicate with a main debug task running on a BPT card. Potentially, the different processors could communicate using a client/server messaging system. Alternatively, a single card (e.g. a X2M card) could run both the main debug task and different hardware debug objects and collect hardware information from other cards over the terminal bus.
  • a single card e.g. a X2M card

Abstract

System debugging includes maintaining a list of debugging function providers in a main debug task and routing console input to a listed debugging function provider. Debugging can also include receiving information from the debugging function providers and transmitting the information to the console for display. Debugging function providers can be object-oriented debug objects. The debugging function providers can send menus of debugging functions or information produced by debugging functions. The debugging can be used to debug a telecommunications terminal.

Description

DEBUGGING SYSTEM
Background This invention relates to system debugging software. Developers write system debugging software to detect system hardware and software problems. Debugger software retrieves and displays information about the state of a system (e.g. hardware register values) and enables a developer to set the system to a specified state. Since systems include different hardware and software elements, developers often write dedicated debugger software from scratch for different systems and individual system elements.
For example, a telecommunications terminal, such as the Litespan™- 2000 Access Network Unit made by DSC™ Communications Corp., includes many different hardware and software elements. A telecommunications terminal connects subscriber lines, such as POTS (Plain Old Telephone Service) and ISDN (Integrated Services Digital Network) lines, to telecommunications exchanges and other telecommunications equipment. Different hardware and software elements handle the subscriber lines, terminal processing, and transmission lines. DSC™ Communications Corp. programmed dedicated debugger software for many of these different elements.
Summary
In general, in one aspect, a method of debugging a system includes maintaining a list of debugging function providers, receiving input from a console, and routing the console input to one of the debugging function providers. Embodiments of the method may include the following features. The method may also include receiving information from debugging function providers for console display. The debugging function providers can be implemented in object-oriented software. The method may be used to debug a telecommunications terminal. The debugging function providers may request addition to the list of debugging function providers. The list may be displayed on a console for operator selection. The debugger function providers may supply a list of debugging functions or submenus. The debugging functions may access both hardware and software system elements.
In general, in another embodiment, a method of debugging a system includes sending information from debugging function providers to a set of main debugging routines for display on a console. In general, in another embodiment, a system for debugging includes a console, one or more debugging function providers, and a set of main debugging routines that maintain a list of debugging function providers and carry information between the console and the debugging function providers.
Embodiments of the system for debugging may include the following features. The set of main debug routines and debugging function providers may communicate using a client/server message system. The set of main debug routines and debugging function providers may both reside on a single card such as an X2M card.
In general, in another aspect, a method of developing debug tools for debugging respective hardware and software elements under control of a user interaction with a console includes providing a common debug task that controls the console to provide a user interface that enables the user to interact with other debug objects and maintains a common programming interface for interaction with all of the debug objects, and generating debug objects for the respective system elements, each of the debug objects providing debug functions for the respective elements and functions that interact with the common debug task via the common programming interface.
Advantages may include one or more of the following. The main debug task along with a set of console functions provide common console input/output (I/O) support for all debug objects. This reduces the amount of programming needed to create a debug object and thus reduces the development time needed to write new debugger software. The main debug task also provides a menu of debug objects to allow a console operator to switch between different debug objects during a debugging session. This enables the console operator to see the interaction between the different system elements as they are being debugged.
Other features and advantages will become apparent from the following description, including the drawings and the claims.
Drawing Descriptions Fig. 1 is a diagram of a console connected to hardware. Fig. 2 is a diagram of a console, a main debug task, and a list of debug objects. Fig. 3 is a diagram of a menu hierarchy.
Fig. 4 is a debugging session flowchart.
Detailed Description Referring to Fig. 1, a console 10 is connected to a system 12. A developer uses the console 10 to view and change the state of the connected system 12. The system shown is a Litespan™-120 telecommunications terminal 12 made by DSC™ Communications Corp. The terminal 12 provides slots that accept different hardware cards (United States Serial No. 08/970,183 filed November 14, 1997, entitled "Telecommunications Terrninar describes a telecommunications terminal that accepts different hardware cards. The terminal 12 connects each inserted card to other inserted cards via a bus (not shown). The different cards include different components and perform different functions. For example, a Bandwidth Allocator, Processor, and Transmission (BPT) card 14 performs terminal management functions in addition to multiplexing and demultiplexing telecommunications signals. A Channel Unit (CU) card 16 handles subscriber line signals. Many cards, including CU 16 and BPT 14, contain processors. An X2M card (a card capable of serving several El channels and running N5.1 protocol software) possesses strong processing capability.
Referring to Fig. 2, the debugging system includes object-oriented software instructions for console functions 19, a main debug task 18, and debug objects 20 and 22. The console functions 19 include routines that handle I/O for a variety of consoles (e.g. dedicated serial or ethernet). The main debug task 18 serves as an intermediary for passing information and commands between the console functions 10 and the debug objects 20 and 22 that provide debugging functions.
Each debug object 20 and 22 derives from a common base class (CDebug) that includes predefined characteristics. Derivation from a common base class speeds debug object 20 and 22 development. Each debug object 20 and 22 can be further programmed to perform specialized debugging functions with respect to associated hardware and software elements 24, 26. For example, one debug object 20 might access hardware registers on a POTS CU card, another debug object 22 might access memory on an ISDN CU card. Yet another debug object (not shown) might access information from software running on the system (e.g. queues, event flags, and history logs).
Though the functions provided by debug objects vary, each debug object 20 and 22 includes a PrintMenu function 26 and a HandleNewInput function 28. The PrintMenu function 26 produces menu information that allows the console operator to control debug objects 20 and 22. The PrintMenu function 26 sends this menu information to the main debug task 18 for processing with other menu information to generate menus that are displayed on the console 10. The HandleNewInput function 28 handles console 10 input routed to the debug object 20 by the main debug task 18. For example, based on console operator input, the main debug task 18 might send to a debug object's HandleNewInput function 28 a message to execute the debug object's 20 third menu choice (not shown). The HandleNewInput function 30 calls the function corresponding to the menu choice. Each debug object 20 and 22 also includes a Constructor 24 that, upon instantiation, sends a request to the main debug task to add the debug object 20 to a main debug task list 34 of debug objects. The main debug task 18 includes a list 34 of pointers to debug objects, a router 32, and a PrintTopMenu function 36. The router 32 sends information from the console functions 19 to debug objects 20 and 22. The router 32 also receives information produced by the debug objects 20 and 22 and sends this information to the console functions 19 for display. The router 32 and console functions 19 eliminate the need to rewrite console I/O functions or calls when developing a new debug object. The PrintTopMenu function 36 produces a menu on the console that includes a list of debug objects. The console operator can use this menu to switch among the different debug objects throughout a debugging session. This offers the console operator the convenience of debugging different system elements in a single session and the ability to debug the system as a whole as different system elements interact. Referring to Fig. 3, the main debug task PrintTopMenu function 36 and debug object PrintMenu functions 26 and 31 allow the console operator to navigate through different menus that include lists of the different debug objects and the debugging functions they provide. The main debug task maintains a menu level variable 71 that indicates which menu should be displayed. When the menu level is zero, the main debug task displays its own menu 37, which includes a list of debug objects. When the console operator chooses one of the listed debug objects (e.g. Debug Object A) the menu level is incremented to level 1. A debug object's PrintMenu function 26 could, for example, produce debug object menus 70 and 72. The PrintMenu function 26 could send any one of these menus to the main debug task for console display. A debug object menu 70 and 72 may include selections for debugging functions the object provides, selections for submenus, and a selection to return to a preceding menu. The PrintMenu function 26 uses the menu level variable to determine which menu to produce. For example, if the menu level is one, a debug object will produce debug object menu 70, but if the menu level is two, the debug object will produce debug object submenu 72. The PrintMenu function adjusts the menu level variable based on console operator input to let the console operator navigate through debug object menus and submenus.
Referring now to Fig. 4, at the beginning of a debugging session, the main debug task sets the menu level at zero (step 39) indicating the main debug task should display its menu of debug objects (step 40). The console operator then selects one of the debug objects (step 42) causing the main debug task to increment the menu level variable (step 44) and route further console input to the chosen debug object's HandleNewInput function.
A debug object's HandleNewInput function processes information sent by the console via the main debug task. If the console operator chooses a debugging function provided by a debug object (step 50), the HandleNewInput function calls the corresponding debug object function (52) and then reproduces the debug object menu at the current menu level for further console operator selection (step 46). If the console operator chooses a debug object submenu (step 54), the menu level variable is incremented (step 58) and the debug object PrintMenu function produces the submenu for display on the console (step 46). If the console operator chooses to return to the preceding menu, the main debug task decrements the menu level variable (step 56). If the menu level variable is zero after the decrementing (step 60), the main debug task displays its own top level menu of debug objects (step 40) and ceases forwarding console input to the previously selected debug object. If the menu level variable is not zero after decrementing (step 60), the debug object's PrintMenu function produces the preceding debug object menu (step 46).
The different debugging objects discussed above can be distributed in many ways. For example, in a telecommunications terminal, each CU card processor could contain its own hardware debug object and communicate with a main debug task running on a BPT card. Potentially, the different processors could communicate using a client/server messaging system. Alternatively, a single card (e.g. a X2M card) could run both the main debug task and different hardware debug objects and collect hardware information from other cards over the terminal bus.
Other embodiments are within the scope of the following claims.
What is claimed is:

Claims

1. A method of debugging a system comprising: maintaining a list of debugging function providers; receiving input from a console connected to the system; and routing console input to one of the listed debugging function providers for further processing.
2. The method of claim 1 further comprising receiving information from a debugging function provider, and transmitting the data to the console for display.
3. The method of claim 1 wherein a debugging function provider comprises an object-oriented debug object.
4. The method of claim 1 wherein further processing by debugging function providers comprises providing information for debugging a telecommunications terminal.
5. The method of claim 1 wherein further processing by debugging function providers comprises providing information for debugging a card inserted into a telecommunications terminal.
6. The method of claim 1 wherein maintaining a list of debugging function providers comprises receiving requests from the debugging function providers for addition to the list.
7. The method of claim 1 wherein routing the console input to a debugging function provider comprises determining which debugging function provider should receive the console input.
8. The method of claim 7 wherein determining which debugging function provider should receive the console input comprises providing a console operator with the list of debugging function providers, and receiving input from the console operator selecting one of the listed debugging function providers.
9. The method of claim 1 wherein further processing by a debugging function provider comprises interacting with other software running on the system.
10. The method of claim 1 wherein further processing by a debugging function provider comprises interacting with a hardware storage device.
11. The method of claim 9 wherein interacting with a hardware storage device comprises reading and writing hardware storage data.
12. The method of claim 1 wherein further processing by a debugging function provider comprises producing a list of different debugging functions provided by the debugging function provider for display and console operator selection.
13. A method of debugging hardware comprising: sending information from debugging function providers to a set of main debugging routines; and sending the information from the set of main debugging routines to a connected console for display.
14. The method of claim 13 wherein sending information from debugging function providers comprises sending hardware debugging information.
15. The method of claim 14 wherein sending information from debugging function providers comprises sending software debugging information.
16. A system for debugging comprising: a console; one or more processors programmed to run at least one debugging function provider; and a processor connected to the console, the processor programmed to run a set of main debug routines that accesses a list of debugging function providers and carries information between the console and the debugging function providers.
17. The system of claim 16 wherein the debugging function providers comprise object-oriented debug objects.
18. The system of claim 16 wherein the set of main debug routines comprise an object-oriented main debug task.
19. The system of claim 16 wherein the processors communicate using a client/server message system in which the set of main debug routines acts as a server and the debugging function providers as clients.
20. The system of claim 16 wherein the one or more processors that run the debugging function providers and the set of main debug routines reside in a telecommunications terminal or one or more cards inserted into the telecommunications terminal.
21. The system of claim 16 wherein a single processor includes both debugging function providers and the set of main debug routines.
22. The system of claim 21 wherein the single processor resides on an X2M card.
23. A method of debugging hardware comprising displaying a list of debugging function providers to a console operator for selection, and responding to console operator selection from the list.
24. The method of claim 23 wherein responding to console operator selection comprises displaying a list of debugging functions provided by the selected debugging function provider for further console operator selection, and responding to the further console operator selection.
25. The method of claim 24 wherein responding to the further console operator selection comprises producing a submenu for further console operator selection.
26. The method of claim 24 wherein responding to the further console operator selection comprises executing a debugging function provided by the selected debugging function provider.
27. The method of claim 26 wherein executing a debugging function comprises interacting with a telecommunications terminal system.
28. The method of claim 26 wherein executing a debugging function comprises interacting with hardware of the system.
29. The method of claim 26 wherein executing a debugging function comprises interacting with software of the system.
30. An electronic storage medium comprising instructions for causing a processor to run a set of main debug routines that maintains a list of debugging function providers and carries information between a connected console and the listed debugging function providers.
31. The electronic storage medium of 30 comprising further instructions that cause the set of main debugging routes to list debugging function providers on the console for console operator selection.
32. The electronic storage medium of 30 wherein the electronic storage medium resides on a telecommunications terminal or on a card inserted into a telecommunications terminal.
33. An electronic storage medium comprising instructions that cause a processor to run a debugging function provider that requests addition to a list of debugging function providers.
34. The electronic storage medium of claim 33 wherein the electronic storage medium resides on a telecommunications terminal or a card inserted into a telecommunications terminal.
35. A method of developing debug tools for debugging respective hardware and software elements under control of a user interacting with a console, the method comprising providing a common debug task that controls the console to provide a user interface that enables the user interaction with respect to other debug objects and maintains a common programming interface for interaction with all of the debug objects, and generating debug objects for the respective elements, each of the debug objects providing debug functions for the respective system elements, and functions that interact with the common debug task via the common programming interface.
36. A system of enabling a user to debug a telecommunications terminal from a console connected to the telecommunications terminal comprising debug objects that provide debug functions for telecommunications terminal system hardware and software, and a common debug task that controls the console to provide a user interface that enables the user interaction with respect to other debug objects and that maintains a common programming interface for interaction with all of the debug objects.
PCT/US1998/026874 1997-12-30 1998-12-18 Debugging system WO1999034290A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU19250/99A AU1925099A (en) 1997-12-30 1998-12-18 Debugging system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US106897A 1997-12-30 1997-12-30
US09/001,068 1997-12-30

Publications (1)

Publication Number Publication Date
WO1999034290A1 true WO1999034290A1 (en) 1999-07-08

Family

ID=21694229

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/026874 WO1999034290A1 (en) 1997-12-30 1998-12-18 Debugging system

Country Status (2)

Country Link
AU (1) AU1925099A (en)
WO (1) WO1999034290A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1220099A2 (en) * 2000-12-28 2002-07-03 Kabushiki Kaisha Toshiba Debugger system, method of extending debug functions of a debugger system and debugger program product
EP1137241A3 (en) * 2000-03-21 2005-01-05 Tenovis GmbH & Co. KG Connecting part assembly for a digital private branch exchange
US8156476B2 (en) 2008-06-10 2012-04-10 Microsoft Corporation Debugging support for tasks in multithreaded environments

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0730227A1 (en) * 1995-03-03 1996-09-04 Sun Microsystems, Inc. System and method for a distributed debugger for debugging distributed application programs
EP0814404A1 (en) * 1996-06-19 1997-12-29 Matsushita Electric Industrial Co., Ltd. Debugging apparatus for debugging a program

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0730227A1 (en) * 1995-03-03 1996-09-04 Sun Microsystems, Inc. System and method for a distributed debugger for debugging distributed application programs
EP0814404A1 (en) * 1996-06-19 1997-12-29 Matsushita Electric Industrial Co., Ltd. Debugging apparatus for debugging a program

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1137241A3 (en) * 2000-03-21 2005-01-05 Tenovis GmbH & Co. KG Connecting part assembly for a digital private branch exchange
EP1220099A2 (en) * 2000-12-28 2002-07-03 Kabushiki Kaisha Toshiba Debugger system, method of extending debug functions of a debugger system and debugger program product
EP1220099A3 (en) * 2000-12-28 2004-04-14 Kabushiki Kaisha Toshiba Debugger system, method of extending debug functions of a debugger system and debugger program product
US8156476B2 (en) 2008-06-10 2012-04-10 Microsoft Corporation Debugging support for tasks in multithreaded environments

Also Published As

Publication number Publication date
AU1925099A (en) 1999-07-19

Similar Documents

Publication Publication Date Title
US6691147B1 (en) Method and apparatus supporting network communications
US9059955B2 (en) System controlling use of a communication channel
US5315705A (en) Communication address management system
US5671408A (en) Network support system
Miranda et al. Appia, a flexible protocol kernel supporting multiple coordinated channels
EP0774853B1 (en) Method and system for graphically displaying and navigating through an interactive voice response menu
RU2150791C1 (en) Telecommunication commutator, which has programmable network protocols, method for its functioning, and method for development of programmable network protocols
JP2883797B2 (en) Apparatus and method for automatically registering identity information of network elements
KR19980701797A (en) Telecommunication switch with universal application program interface for standardized interactive call processing communication
EP1331556B1 (en) Server-based computer environment
US7562129B1 (en) Subscription management system for data communication network
KR20000069516A (en) Method and device in telecommunications network
US5365581A (en) Telephonic switching system with automatic port assignment capability and method
US8739042B2 (en) User interface design for telecommunications systems
KR900005321A (en) Application, information service implementation method and network operation system
US5764914A (en) Network system for connecting to a network node from terminal
WO1999034290A1 (en) Debugging system
JP2883796B2 (en) Logical Integration of Multiple Network Elements in Communication Management Network
EP1146688B1 (en) Execution sets for generated error - logs
KR20020074138A (en) System and Method to manage customer's avatas on Internet
WO1997041657A1 (en) Method and apparatus for emulating a digital cross-connect switch network
AU691341B2 (en) A flexible call record mechanism
US6868542B1 (en) Method and apparatus for providing reliable interoperation of a plurality of independent software modules
KR100313277B1 (en) PC communication service receiving device having screen selection function by shortcut icon and its method
EP0114357A2 (en) Controlling multiple distributed computations in a multi cpu environnment from a single port

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase