WO2007121658A1 - Procédé de débogage et appareil pour effectuer un développement de services de classe télécoms guidé par modèle - Google Patents

Procédé de débogage et appareil pour effectuer un développement de services de classe télécoms guidé par modèle Download PDF

Info

Publication number
WO2007121658A1
WO2007121658A1 PCT/CN2007/001050 CN2007001050W WO2007121658A1 WO 2007121658 A1 WO2007121658 A1 WO 2007121658A1 CN 2007001050 W CN2007001050 W CN 2007001050W WO 2007121658 A1 WO2007121658 A1 WO 2007121658A1
Authority
WO
WIPO (PCT)
Prior art keywords
code
debugging
primitive
remote
information
Prior art date
Application number
PCT/CN2007/001050
Other languages
English (en)
French (fr)
Inventor
Guowen Jiang
Zejian Ju
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07720624A priority Critical patent/EP2017983A4/en
Priority to CN2007800004212A priority patent/CN101401333B/zh
Publication of WO2007121658A1 publication Critical patent/WO2007121658A1/zh
Priority to US11/970,621 priority patent/US20080148237A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3664Environments for testing or debugging software
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0062Provisions for network management
    • H04Q3/0075Fault management techniques
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1305Software aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13162Fault indication and localisation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13251Restricted service, class of service

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a debugging method and apparatus for carrier-class service development based on model driving.
  • MDA is a burst mode with a highly abstract model as the core. By constructing a model, it can automatically generate efficient and correct code, so that software developers no longer need to face endless syntax errors, memory leaks and other issues. As a software development model that improves production efficiency and reduces software development complexity, MDA has increased its application in the industry.
  • Software debugging is inevitable during the software development process. As an indispensable part of the software development process, software debugging can detect errors caused by negligence or poor consideration during development. In the MDA development mode, although the probability of error has been greatly reduced, the developer's level of abstraction is higher, making the underlying error more concealed, thus making the wrong positioning more difficult. To this end, the debugger is required to be more intelligent, and the error of the running of the underlying program can be fed back to the upper layer model and the script code to realize the graphic debugging.
  • a simple model running simulator is usually provided for software debugging.
  • This simulator can simulate the running process of the program. During the simulation process, you can find logic errors that may exist in the program.
  • the generated business generated code can be compiled into a Windows or unix program by calling an external compiler, and then controlled to run in the program during the running of the program.
  • the execution track of the program is dynamically displayed on the graph.
  • the above-mentioned commercial development tools for supporting model development are generally oriented to embedded devices, and can be easily implemented for the development and debugging of logically simple business software, but the tool is not very good for logic complex carrier-class business software.
  • the ground meets the requirements for use.
  • the debugger is not a real debugger, but an emulator. So some of the more concealed in the real operating environment Errors are difficult to find during simulation, and it is difficult to locate during actual operation.
  • MDA-based services are typically developed on a personal PC and compiled and debugged on the real-world operating environment of the business (various unix servers). In this case, model-level debugging can only be done remotely.
  • commercial software that implements remote compilation and debugging such as MagicC++ of MagicUnix, provides a Visual C++ development environment on Windows.
  • remote compilation and debugging are implemented through telnet or a protocol defined by itself or ftp.
  • Embodiments of the present invention provide a debugging method and apparatus for carrier-class service development based on model driving.
  • the embodiment of the present invention is implemented by the following technical solutions.
  • the embodiment of the present invention provides a debugging method for carrier-class service development based on a model driver.
  • the code debugger is debugged according to the code reverse check primitive.
  • the combination of information and model display enables model-driven graphics and text debugging.
  • An embodiment of the present invention provides a debugging apparatus for performing carrier-class service development based on a model driver, where the apparatus includes:
  • the debugging control module is used to control the debugging operation of the program file, and the debugging information of the code debugger is combined with the model display according to the code to check the picture element, and the model-driven graphic and text debugging is realized.
  • the embodiment of the present invention provides an MDA-based debugging capability for a carrier-class service development tool, and realizes real debugging without using any simulator.
  • 2 is a process diagram of a remote process creation process according to an embodiment of the present invention
  • 3 is a schematic diagram of correspondence between code and model primitives according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of state transition of a state diagram according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of content and insertion position of an insertion code according to an embodiment of the present invention.
  • Figure 6 is a schematic illustration of an embodiment of the apparatus of the present invention.
  • the embodiment of the invention provides a debugging method and device for carrier-class service development based on model driving.
  • the command line code debugger is used at the bottom of the graphic debugger, and the control service software runs in a real running environment, and the upper layer will be
  • the debug information of the code debugger is combined with the model display to realize the graphic and text debugging in the real environment.
  • a first embodiment of the present invention provides a method for debugging a carrier-class service based on a model.
  • the remote debugging operation is taken as an example in the embodiment.
  • the operation process is as shown in FIG. 1 and includes the following steps:
  • Step 1 Implement synchronous operation between local and remote files.
  • the synchronization operation can be implemented by remote file mirroring, file timestamp comparison, etc., and the file synchronization operation is dynamically performed according to changes of local and remote files;
  • Step 2 Call the compiler and code debugger program on the remote server
  • This embodiment applies the client (client) / server (server) way, proposes an abstract process model, implements the Process (process) interface in java, from j va can call the remote program like calling a local program,
  • the upper IDE (Integrated Development Environment) code can interact with the remote program without any changes.
  • the remote abstract process model and the process of calling the remote process are described in detail in Figure 2 and Figure 6.
  • Step 3 Parse the compile/debug information of the remote file called above;
  • the corresponding parsing module provides a unified access interface to the upper layer, which can parse the remote compiling result and control the remote debugging process.
  • Step 4 Control a debugging process of the parsed program file
  • the debugging operation is completed when each primitive in the process generates the corresponding code and is compiled into an executable program. In the process of tracking the execution process of the program, it is inevitable to insert breakpoints and execution orders in some places.
  • Step operation. includes: code single step, script single step and picture single step.
  • the code debugger supports single-step at the line level. By sending a step, next, or finish command to the code debugger, you can implement code step-by-step, skip, and If.
  • the jump indicates that the jump to the corresponding method, for the script logic block primitive, the jump indicates that the user script is jumped; the skip is a normal step over a primitive; the jump indicates Jump out of the current context. If it is currently in a state diagram, it will jump out of this state diagram.
  • the single step jump of the primitive in the single step jump of the primitive, it may be transferred to other method primitives, or may be jumped to the user script corresponding to the current script primitive by the graphical view, and the subsequent single-step operation is converted into a script step.
  • the single step jump in the other case is the same as the single step skip operation.
  • script single-step jump-in if the script corresponds to the code one by one, just step through the code corresponding to the script. Where there is no function call, the script step-by-step is the same as the single-step skip operation.
  • a general code debugger such as gdb, itself provides a catch command for setting catchpoint.
  • a catchpoint is a breakpoint-like breakpoint that stops the program when loading a dynamic library, throwing a C++ exception, or catching a c ++ exception. Come down. So you can use the catch catch command to stop when a C++ exception is caught, and then use a single-step command, such as next, to jump to the code that handles the exception.
  • the position on the primitive can be reversed to implement the primitive Debugging. The method of retrieving the primitive according to the code is described later.
  • the glibc library is the cxa_begin_catch function, which is a library function provided by the glibc library to capture C++ exceptions.
  • Another way to determine the next primitive is to use no breakpoints, but after the user issues a single-step command, the command code debugger keeps running the single-step command, checking the current line of code each time the single-step is stopped. Which picture element belongs to. This includes three situations:
  • the current line of code belongs to another element.
  • the picture element is successfully completed in one step, and the picture element is single stepped.
  • This method does not need to predict all possible jump positions, and does not need to insert additional breakpoints.
  • the advantage of the single-step method of the code line is obvious. However, it does not apply when there is a large loop in the primitive.
  • the until command can be used with a parameter to specify a stop position. In this way, the code debugger can skip the loop by inserting a breakpoint at this stop position, so the efficiency will be greatly improved [3 ⁇ 4
  • one of the methods can be selected by comparing the difficulty and effect of the implementation of the two schemes.
  • Step out There are two ways to single-step jump out of a primitive. One is to set a temporary breakpoint at the exit of all current end primitives, and then command the code debugger to run the program. When the program stops at a breakpoint, the command code debugger continues to step through the current context.
  • the other method is based on the assumption that for each state diagram, there is a function corresponding to it, so the command debugger is continuously commanded to run the finish command to jump out of the current function. If it finds that the current context is jumped out, including the jump-out graph. Meta code, or jump out of the current state diagram, step out and end.
  • the single step jump of the script can also take the command code debugger to run the finish command continuously until the current script scope is jumped out.
  • debugging operations include: start running, pause running, end debugging, etc., mainly to send different commands to the code debugger, and update the interface display.
  • Setting a breakpoint on an element can be as fast as inserting a breakpoint at the entry to the element.
  • find the line of code corresponding to a line script and directly command the code debugger to insert a breakpoint. Since the general code debugger supports the setting of conditional breakpoints, you can set conditional breakpoints on primitives or scripts.
  • debugging also includes viewing and modifying local variables, global variables, viewing the value of expressions, viewing and modifying memory regions, disassembling code segments, viewing and modifying registers, viewing call stacks, etc., which can be used directly.
  • the function of the code debugger is obtained.
  • the process involves the IDE positioning the primitive according to the reported code, that is, the corresponding primitive is located in the reverse direction according to the position of the code.
  • the embodiment of the present invention provides the following three methods to implement the code according to the code. Reverse check primitive:
  • Figure 3 shows the correspondence between the primitive and the code.
  • the left side is an implementation flow of the user logic.
  • the implementation flow consists of the block primitives connected by the migration line.
  • the migration line specifies the execution flow of the program.
  • the migration line TO executes to the logicO logic block primitive, and then executes to the condO conditional branch primitive through the migration line T1.
  • the migration line itself can also be logical or code generated.
  • On the right is a sample code that is automatically generated according to this process.
  • Each primitive in the user logic implementation process generates a corresponding code.
  • the start primitive generates the 0th to 2nd lines of code; logicO logic
  • the block primitive corresponds to the 4th to 6th lines of code;
  • the condO conditional branch primitive corresponds to the 7th to 11th lines of code.
  • the corresponding relationship between the primitive and the code line number is saved in the project.
  • the current code line number is obtained from the debugger, and then directly mapped to the primitive by the corresponding relationship. For example, when debugging, the debugger encounters a breakpoint to stop running. In the IDE, it should show which element the program stopped to.
  • the process is: The program encounters a breakpoint, stops running, stops at the memory address AA; Source code The debugger converts the AA into the LL line of the source code file SS according to the debugging information in the program; the IDE finds the corresponding primitive identifier FF according to the LL line of the SS file according to the correspondence between the primitive and the generated code line number; According to this flag, the stop position of the current program is displayed.
  • This correspondence is also used when the user adds a breakpoint, but the direction is reversed.
  • the process is: The user selects a primitive FF on the IDE interface, and then adds a breakpoint on it; the IDE corresponds to the primitive and the code line number. Relationship, find the code corresponding to the primitive FF in the L1 to L2 line of the SS file; the IDE sends an instruction to the source code debugger to set a breakpoint in the L1 line of the SS file; the source code debugger is based on the debug information of the debugged program, A breakpoint is set at the memory address AA corresponding to the L1 line.
  • a report code is inserted in the place where the graphic display is affected, and the graphic update information is fed back to the IDE.
  • the report information After inserting the report code, whenever the code enters a new picture element during debugging, the report information will be transmitted to the IDE, and the report information will be very frequent, so it is not necessary to update the graphic display every time, only the code is debugged in the target program. After the device is paused, the graphic display can be updated according to the last report information.
  • a source state can have multiple exit migration lines to several different destination states, or multiple exit migration lines to the same destination state, as shown in Figure 4, in Figure 4, reusable state.
  • the picture element Re-stateO has three exit migration lines, the Tl and ⁇ 2 migration lines all migrate to the logic block element logicO, and the T3 migration line migrates to the state element stateO.
  • the inserted code needs to be placed at the exit location of each state.
  • the report information includes the ID of the current element and the ID of the exit line to be taken. Based on all of these escalation information, the IDE can reconstruct the trajectory of the entire program.
  • the escalation code is preferably defined as a macro format, which can be defined as follows:
  • REPORT will be expanded into a report code. This macro is not defined in the distribution. All report codes will be defined as empty and will not affect the release code.
  • the EPORT command reports the primitive information that the program has run to the IDE through network communication or pipeline. After the IDE receives these tracks, it saves them in a track list. When the program pauses, the tracks can be displayed. As shown in Figure 5, the program starts from the start element start, at the exit of the start element. At the same time, the Report command reports the ID of the start primitive and the ID of the migration line TO and the current frame ID of the current thread to the IDE, and the IDE records the information. When the program finally runs to the logicl state diagram, the run track will be identified and the current position will be identified.
  • the remote server configure the remote server's ip, port, user name, password and other information in the IDE; the IDE establishes a connection with the remote server through the network according to the configured information, if the configuration information is wrong, such as the port is wrong, If the password is incorrect, the connection will fail, the remote process cannot be created, and the IDE will notify the user to modify the configuration. If the connection is successful, the abstract process module creates a server proxy locally based on the connection information; the IDE issues an instruction to the server proxy to create the process, the server proxy sends the instruction to the remote server through the established network connection, and the remote server creates the remote process.
  • the remote server creation process fails, a failure message is returned to the server agent, which will notify the IDE that the creation process failed. If the remote server creation process is successful, the information of the created remote process is sent back to the server agent. Based on this information, the server agent creates a remote process agent that establishes a connection with the remote process based on the information sent back by the remote server. The server agent returns the remote process proxy object to the IDE.
  • the remote process proxy object implements the same Process interface as the local process object. The IDE can use the remote process proxy just like a local process.
  • the remote server will receive a notification signal. After receiving the notification signal, the remote server sends a process end event to the remote server proxy object connected to it. After receiving the process end event, the remote server agent finds the corresponding remote process proxy object according to the process number, activates the thread waiting for the end of the process, and the remote process ends.
  • the IDE sends an end process command to the remote server agent where the process proxy object is located.
  • the remote server agent sends a shutdown process command to the remote server connected to it, and the remote server turns off the corresponding remote process by killing.
  • the remote server receives the notification signal, and the remote server sends a process end event to the remote server agent connected thereto, and after receiving the process end event, the remote server agent finds the corresponding remote according to the process number.
  • the process proxy object activates the thread waiting for the process to end, and the remote process ends.
  • the abstract process module encapsulates the information of the remote process, and the IDE configures the remote server. After the information, you can use the remote process just like the local process. There is no limit to the process to be run, which greatly facilitates the development of remote compilation and debugging.
  • a second embodiment of the present invention provides a debugging device for performing carrier-class service development based on a model driver.
  • the device structure is shown in FIG. 6.
  • the device includes: a file synchronization module, an abstract process module, a parsing module, and a debugging control module.
  • the file synchronization module is configured to perform operations of synchronizing local files and remote files, and the synchronization operations may be implemented by remote file mirroring, file time stamp comparison, etc., and dynamically perform file synchronization operations according to changes of local and remote files.
  • the abstract process module is connected to the remote server, and the remote server proxy can be created according to the information of the remote server configured by the IDE, the remote server proxy is used to establish a connection with the remote server, perform information interaction with the remote server, and feedback according to the remote server.
  • the remote process information creates a remote process agent that establishes a connection with the remote process according to the information fed back by the remote server, and the remote server agent returns the process proxy object to the IDE, so that the process proxy object and the local process object use the same process interface.
  • the IDE can get remote processes just like getting local processes. '
  • the parsing module is configured to parse the output information of the remote compiler and the code debugger, determine whether the remote compiling operation is abnormal, and parse the return information of the code debugger.
  • the debugging control module is configured to control the debugging operation of the program file, so that the control information and the running result of the code debugger in the debugging process are combined with the model display and the control command to realize the real graphic debugging.
  • the embodiment of the present invention provides an MDA-based debugging capability for a carrier-class service development tool, and achieves true graphics debugging without using any simulator.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Description

一种基于模型驱动进行电信级业务开发的调试方法及装置 技术领域
本发明涉及通讯技术领域, 尤其涉及一种基于模型驱动进行电信级业务开发的调试 方法及装置。
发明背景
现代软件变得越来越庞大, 复杂度越来越高, 因此, 软件的设计和实现的难度也变 得越来越大, 进而导致了软件开发模式和软件开发工具的发展和进化。从软件开发的进 化过程来看, 从开始的汇编语言, 到过程化语言, 再到面向对象的语言, 开发工具从开 始的编辑器 +汇编器 /编译器,到功能全面的集成开发环境, 以及现在正在不断普及和发 展的 MDA (模型驱动架构), 软件开发的抽象层次越来越高。
其中, MDA是一种以高度抽象的模型为核心的幵发模式, 通过构造模型可以自动 生成高效正确的代码, 使得软件开发人员无需再面对无休止的语法错误、 内存泄漏等问 题。 MDA作为一种提高生产效率、 降低软件开发复杂度的软件开发模式, 在业界的应 用曰益增多。
在软件开发过程中不可避免要进行软件调试。软件调试作为软件开发流程中必不可 少的一部分, 能够发现开发过程中由于疏忽或考虑不周造成的各种错误。 在 MDA开发 模式下, 虽然出现错误的几率已经大大减少, 但由于开发人员所处的抽象层次更高, 使 得底层错误变得更加隐蔽, 这样, 错误的定位也就更加困难。 为此, 便要求调试器更加 智能, 能够将底层程序运行的错误反馈到上层的模型和脚本代码中, 实现图文调试。
在现有的基于 MDA的集成开发环境中, 为实现软件调试功能, 通常均设置有简单 的模型运行模拟器。这种模拟器能够模拟程序的运行过程, 在模拟过程中便可以发现程 序中可能存在的逻辑错误, 这是一种比较简单的调试器。 比如在 Rhapsody, TeleLogic Tau, 以及 Rational Rose for RT等商业软件中, 可以将开发的业务生成代码, 通过调用 外部编译器编译成 Windows或 unix程序, 然后控制这些程序运行, 在程序运行过程中 在模型图上动态显示程序的执行轨迹。
上述现有的支持模型开发的商业开发工具一般都是面向嵌入式设备的,对于逻辑简 单的业务软件的开发和调试均可以方便实现,但是对于逻辑复杂的电信级业务软件该工 具却无法很好地满足使用要求。
另外, 上述开发工具中因为被调试的程序没有在最终运行环境中运行, 因而所述的 调试器不是真正的调试器, 而是一种模拟器。这样在真实运行环境中的一些比较隐蔽的 错误在模拟时很难发现, 在实际运行过程中发现了又很难定位。
除了上述在本地进行编译和调试外, 开发基于 MDA的电信业务时还存在远程编译 和调试的需求。 基于 MDA的业务一般会在个人 PC上进行开发, 在业务的真实运行环 境 (各种 unix服务器)上进行编译和调试。 这种情况下模型级别的调试只能远程操作。 目前实现远程编译和调试的商业软件, 如 MagicUnix公司的 MagicC++, 提供了一个 Windows上类 Visual C++的开发环境, 同时通过 telnet或自己定义的协议、 ftp等协议实 现远程的编译和调试。
还有一些软件通过 "桩程序"的方式来支持远程编译和调试, 比如 UniWin, 在本 地提供了调试器 gdb, 编译器 gcc等服务器程序的 "桩程序", 这些"桩程序 "是远端程 序的一个本地代理, 他们的作用就是完成本地和远端的命令和应答传输, 实现一个简单 中继的功能。
目前的远程编译调试软件都没有提供基于模型开发的功能,还是完全的手工编码方 式, 这种方式的开发对越来越庞大的软件业务已经有些力不从心; 并且, "桩程序" 的 方式需要为每一个要调用的远程程序做一个 "桩程序", 无法执行没有相应桩程序的远 程程序, 扩展性不好。
发明内容
本发明实施例提供一种基于模型驱动进行电信级业务开发的调试方法及装置。 本发明实施例是通过以下技术方案实现的- 本发明实施例提供一种基于模型驱动进行电信级业务开发的调试方法,在进行调试 操作时, 根据代码反查图元, 使代码调试器的调试信息与模型显示相结合, 实现基于模 型驱动的图文调试。
本发明实施例提供一种基于模型驱动进行电信级业务开发的调试装置,所述装置包 括:
调试控制模块, 用于控制程序文件的调试操作, 根据代码反査图元, 实现代码调试 器的调试信息与模型显示结合起来, 实现基于模型驱动的图文调试。
由上述本发明实施例提供的技术方案可以看出:本发明实施例为电信级业务开发工 具提供了基于 MDA的调试能力, 实现了不使用任何模拟器, 达到真正的图文调试。 附图简要说明
图 1为本发明所述方法一种实施例操作流程图;
图 2为本发明一种实施例远程进程创建过程图; 图 3为本发明实施例代码和模型图元的对应关系示意图;
图 4为本发明实施例状态图的状态迁移示意图;
图 5为本发明实施例插入代码的内容和插入位置示意图;
图 6为本发明所述装置一种实施例示意图。
实施本发明的方式
本发明实施例提供了一种基于模型驱动进行电信级业务开发的调试方法及装置,在 图文调试器的底层使用命令行代码调试器, 控制业务软件在真实的运行环境中运行, 在 上层将代码调试器的调试信息与模型显示相结合, 实现真实环境下的图文调试。
本发明实施例一提供了一种基于模型驱动进行电信级业务开发的调试方法,本实施 例以远程调试操作为例进行说明, 所述操作过程如图 1所示, 包括如下步骤:
步骤 1 : 实现本地与远程文件的同步操作;
所述同步操作可以通过远程文件镜像、文件时间戳比较等方法来实现, 根据本地和 远程文件的改变动态执行文件同步操作;
步骤 2: 调用远程服务器上的编译器和代码调试器程序;
本实施例应用 client (客户) /server (服务器) 的方式, 提出了一种抽象进程模型, 实现了 java中的 Process (进程)接口, 从 j va中可以象调用本地程序一样调用远端程 序, 上层 IDE (Integrated Development Environment, 集成开发环境)代码不用任何改动 就可以与远端程序进行交互。 该远程抽象进程模型及调用远程进程过程详见图 2及图 6 描述。
步骤 3: 对上述调用的远程文件的编译 /调试信息进行解析;
由于不同的编译器 /调试器有不同格式的输出, 针对这些输出, 由相应的解析模块, 对上层提供了统一的访问接口, 可以实现对远端编译结果进行解析, 及控制远端调试过 程。
步骤 4: 控制所述解析后的程序文件的调试过程;
对编译生成的程序文件进行调试的过程如下所述:
在模型上调试时, 需要实现在图和代码中跟踪业务的运行轨迹、执行单步操作、 设 置断点、 显示调用堆桟、 实时显示和修改变量值等操作。
调试操作是在流程中每个图元都生成了相应的代码,并编译成可执行程序的情况下 完成的, 在跟踪程序执行流程的过程中, 不可避免需要在部分位置插入断点、执行单步 操作。 所述单步操作包括: 代码单步、脚本单步和图元单步。代码调试器支持代码行级别 的单步, 通过向代码调试器发送 step、 next, 或者 finish命令, 可以分别实现代码单步 跳入、 跳过和 If兆出。
脚本单步中, 跳入、 跳过和跳出的语义与 C/C++代码调试时的语义一样, 都是针对 函数调用的不同单步方法。
图元单步中, 对于方法调用图元, 跳入表示跳转到相应的方法, 对于脚本逻辑块图 元,跳入表示跳入用户脚本;跳过是正常的步过一个图元;跳出表示跳出当前的 context, 如果当前处于某个状态图, 将跳出这个状态图。
下面分别针对单步操作中的跳入、 跳过及跳出进行说明:
单步跳入:
对于单步跳入, 在图元单步跳入中, 可能会转到其他方法图元, 也可能由图形视图 跳转到当前脚本图元对应的用户脚本, 之后的单步操作转为脚本单步。其他情况下的单 步跳入与单步跳过操作相同。
对于脚本单步跳入, 如果脚本与代码一一对应, 只要对脚本对应的代码进行单步跳 入即可。 在没有函数调用的地方, 脚本单步跳入与单步跳过操作相同。
单步跳过:
对于单步跳过图元时, 需要确定下一个图元的位置。 如果已经处于一个结束图元, 单步跳过图元与单步跳出操作相同。
为了确定下一个图元的位置。一种方法是 IDE搜索下一步所有可能的图元,在它们 入口处设置临时的断点, 然后命令代码调试器运行被调试的程序。 当程序停在某一个断 点处时,即可由此确定下一个图元的位置。关于插入的临时断点,可以每次单步前插入, 单步后删除。 因为这些断点只对这一次单步有用, 在其他情况下没有用处, 并且断点的 数量一般很少, 一个或几个, 插入和删除不会消耗很多时间。
如果在状态图生成的代码中抛出了某个异常, 而代码中没有捕获这个异常, 那么程 序将不经过所述设置的断点而跳出当前的状态图。异常发生时调用堆栈会不断回滚, 直 到搜索到一个可以处理该异常的父函数为止。 一般的代码调试器, 比如 gdb, 本身提供 了 catch命令用于设置 catchpoint, catchpoint是一种类似 breakpoint的断点,可以在加载 一个动态库、 抛出 c++异常或捕获 c++异常时将程序停下来。 因此可以使用 catch catch 命令在捕获到一个 C++异常时停下来, 然后使用一个行单步命令, 如 next就可以跳转到 处理该异常的代码处。根据该处的代码位置, 可以反推出图元上的位置, 从而实现图元 调试。 该根据代码反查图元的方法祥见后续介绍。
由于不是所有的代码调试器都支持 catch catch命令, 经过对 catch catch命令进行分 析发现,当捕获一个 C++异常程序停下来时,代码实际上停在某个捕获异常的库函数上, 比如在 linux上的 glibc库中是— cxa_begin_catch函数, 该函数是 glibc库提供的一个捕 获 C++异常时跳转的库函数。 在使用不支持 catch catch命令的代码调试器时, 可以在这 个库函数处设置断点, 达到与 catch catch命令同样的效果。 通过这种方法可以处理 C++ 异常。
另一种确定下一个图元的方法是不用断点, 而是在用户发出图元单步的命令后, 命 令代码调试器不断运行单步命令,每次单步停止时,检査当前代码行是属于哪一个图元。 这时包括三种情况:
一种是当前代码行仍然属于当前图元,这种情况下继续命令代码调试器运行单步命 令;
另一种情况是当前代码行不属于任何一个图元, 需要代码调试器继续运行单步命 令;
最后一种情况是当前代码行属于另一个图元, 这时图元单步正常完成, 图元单步停 止。
这种方法不需要预测所有可能的跳转位置, 不需要插入额外的断点, 在图元中执行 的代码行不多时, 代码行单步的方法优点很明显。但在图元中存在很大的循环时, 不能 适用。 对于 gdb代码调试器, 此时可以采用代码调试器中提供的 until命令, 用于跳过 大循环。 until命令实际上仍然通过指令单步的方法执行,根据 CPU速度的不同, 比 next 单步快几到十几倍。 until命令可以与一个参数配合使用, 用于指定一个停止位置。这样 代码调试器可以通过在这个停止位置插入一个断点的方法将循环跳过,这样效率会大大 提[¾
因此, 对于代码行单步的方法, 可以使用 until命令来跳过大循环, 此时需要知道 大循环结束位置的行号。对于插入断点的方法, 需要预测所有可能单步到达的位置, 然 后在这些位置插入断点。在实现时可以通过比较所述两种方案的实现难度和效果, 从而 选择其中一种方法。
对于脚本的单步跳过, 与脚本单步跳入类似, 如果脚本与代码一一对应, 只要对脚 本对应的代码进行单步跳过即可。
单步跳出: 对于图元单步跳出有两种方法,一种是在当前的所有结束图元的出口设置临时的断 点, 然后命令代码调试器运行程序。 当程序停在某一个断点后, 命令代码调试器不断单 步, 直到跳出当前的 context。
另一种方法基于这样一个假设: 对于每一个状态图, 都对应有一个函数, 因此, 不 断命令代码调试器运行 finish命令跳出当前的函数, 如果发现跳出了当前的 context, 包 括跳出跳入的图元代码, 或跳出当前的状态图, 单步跳出结束。
对于用户脚本, 因为用户可能会在脚本的中间某一行跳出, 比如 return语句, 如果 不解析用户的脚本, 则不能确定脚本到底有几个出口。所以脚本的单步跳出也可以采取 命令代码调试器不断运行 finish命令的做法, 直到跳出当前的脚本范围。
如果允许脚本中含有伪同步代码, 则只能使用不断单步的方法。
除了上述的单步调试操作外,调试操作还包括:开始运行、暂停运行、结束调试等, 主要是向代码调试器发送不同的命令, 并更新界面显示。
对图元设置断点的操作可以同插入代码的方法一样, 在图元入口处插入断点。对脚 本设置断点时, 找到某行脚本对应的代码行, 直接命令代码调试器插入断点即可。 由于 一般的代码调试器都支持条件断点的设置, 因此可以对图元或脚本设置条件断点。
另外, 调试时还包括查看和修改局部变量、 全局变量, 查看表达式的值, 査看和修 改内存区域, 反汇编代码段, 查看和修改寄存器, 查看调用堆栈等, 所述这些操作可以 直接使用代码调试器的功能获得。
所述调试操作过程中, 涉及到 IDE根据上报的代码定位图元的过程, 即, 根据代码 的位置, 反向定位出对应的图元, 本发明实施例提供了如下三种方法来实现根据代码反 查图元:
1 )在每个图元记录对应的代码的行号, 根据行号反查图元;
如图 3所示为图元与代码的对应关系, 左边是用户逻辑的一个实现流程, 实现流程 由迁移线连接起来的块图元组成, 迁移线指定了程序的执行流程, 从开始图元经过迁移 线 TO执行到 logicO逻辑块图元,之后经过迁移线 T1执行到 condO条件分支图元。迁移 线本身也可以带有逻辑, 也可以生成代码。 右边是根据这个流程自动生成的代码样例, 用户逻辑实现流程中的每个图元都会生成相应的一份代码, 如图 3中, 开始图元生成了 第 0到第 2行代码; logicO逻辑块图元对应第 4到第 6行代码; condO条件分支图元对 应第 7到第 11行代码。 在工程中保存了所述图元与代码行号的对应关系, 在进行调试 时, 从所述调试器中获取当前的代码行号, 之后通过所述对应关系直接定位到图元上。 例如,调试时被调试程序遇到一个断点停止运行,在 IDE中应该显示程序停止到哪 个图元上, 此过程为: 程序遇到断点, 停止运行, 停在内存地址 AA处; 源代码调试器 根据程序中的调试信息,将 AA转化为源代码文件 SS的 LL行; IDE根据图元和生成代 码行号的对应关系, 根据 SS文件的 LL行找到对应的图元标识 FF; 运行界面根据这个 标识, 显示当前程序的停止位置。
用户添加断点时也会使用这种对应关系, 不过方向相反, 其过程为: 用户在 IDE界 面上, 选中一个图元 FF, 然后在上面添加断点; IDE根据图元和代码行号的对应关系, 找到图元 FF对应的代码在 SS文件的 L1到 L2行; IDE向源代码调试器发送在 SS文件 的 L1行设置断点的指令;源代码调试器根据被调试程序的调试信息,在 L1行对应的内 存地址 AA处设置断点。
从行号到图元的对应关系可以使用如下格式描述-
< ?xml version= " 1 . 0 " encoding="UTF-8 " ?>
<method name= " s impleFunc tion " >
<f igure id=" cond0 "
f ilename="NewService . cpp"
startline=" 07 "
endline=" 11 " />
<f igure />
< /method> 其中可以看出, condO逻辑块图元生成的代码对应 NewService.cpp文件的第 7行到 第 11行。 '
2)在源代码中添加特殊的注释信息, 根据注释信息反査图元;
在由图元生成代码时,使用一些特殊的注释信息来表明当前一部分代码对应哪个图 元, 如, 可以在注释中添加 XML标签, 然后使用已有的 XML解析器对生成的源代码 进行解析。 当知道一个行号时, 可以向前寻找相应的注释信息, 分析注释信息就可以找 到对应于哪个图元。
3 )在源代码中插入特殊的上报代码, 根据上报代码反查图元;
在生成的源代码中, 在影响图形显示的地方插入上报代码, 用以将图形更新信息反 馈给 IDE。
比如在一个图元对应的代码执行结束位置插入上报代码, 当程序运行到这个位置 时, 上报代码将这个图元的信息反馈给 IDE, IDE会记下这个信息, 留待以后在图上显 示运行轨迹。
在插入上报代码后,调试时每当代码进入一个新的图元,都会有上报信息传到 IDE, 上报信息会非常频繁, 因此不需要每次都更新图形显示, 只需要在目标程序被代码调试 器暂停下来后, 根据最后一次的上报信息更新图形显示即可。
下面介绍插入上报代码的方法:
在状态图中, 一个源状态可以有多条出口迁移线到几个不同的目的状态, 或存在多 条出口迁移线到同一个目的状态, 如图 4所示, 在图 4中, 可重用状态图元 Re一 stateO 有三条出口迁移线, Tl、 Τ2迁移线都迁移到逻辑块图元 logicO, T3迁移线迁移到状态 图元 stateO。 在这种情况下, 为了标识状态跃迁的路径, 需要将插入的代码放在每个状 态的出口位置。一个图元有几个出口, 就在几个地方插入上报代码。 因此 Re—stateO图 元生成的代码中将会有三条上报信息, 分别对应三个出口点。上报信息包括当前图元的 ID以及要走的出口线的 ID。 IDE根据所有的这些上报信息, 即可重新构造出整个程序 运行的轨迹。
对于状态图元中的脚本图元, 因为脚本中不需要显示运行轨迹, 根据代码生成的需 要, 脚本图元中不能有 return语句, 不能主动抛出异常, 因此不论脚本逻辑中有多少个 出口, 脚本图元始终只有一个出口, 所以对于脚本图元只需要在脚本图元结束位置插入 上报代码。
对于带有脚本的迁移线, 因其轨迹已经被起始点的状态图元标出, 所以不必插入上 报代码。
为了支持 debug版和 release版使用同一份代码,上报代码最好定义为宏的格式,可 以采取如下定义方法:
#ifdef — USE— FEEDBACK— CODE
# define REPORT ( . . . ) • 〃反馈代码
#else
# define REPORT (…) //发行版不加反馈代码
#endif
这样在上报信息时, 只要简单地调用 REPORT(...)就可以了。 在调试版中定义宏
—USE—FEEDBACK— CODE, REPORT将会展开成上报代码, 在发行版中不定义这个宏, 所有的上报代码都将被定义为空, 不会对发行版代码产生影响。 在调试过程中, 随着被调试程序的运行, EPORT指令通过网络通信或管道, 将程 序运行过的图元信息顺序上报给 IDE。 IDE收到这些轨迹后, 将其保存在一个轨迹列表 中, 当程序暂停运行时, 可以将这些轨迹显示出来, 如图 5所示, 程序从开始图元 start 开始执行,在 start图元的出口处, Report命令会将 start图元的 ID和迁移线 TO的 ID以 及当前线程的当前桟帧标识上报给 IDE, IDE将该信息记录下来。 当程序最终运行到 logicl状态图时, 运行过的轨迹会标识出来, 当前位置也会标识出来。
' 下面对图 2用户创建远程进程的过程进行详细说明, 包括:
首先, 启动远程服务器, 在 IDE中配置远程服务器的 ip、 端口、 用户名、密码等信 息; IDE根据所述配置的信息通过网络与远程服务器建立连接, 如果配置信息有错, 如 端口写错、密码错误等,连接将会失败,无法创建远程进程, IDE将通知用户修改配置。 如果连接成功, 抽象进程模块根据连接信息在本地创建一个服务器代理; IDE向服务器 代理发出创建进程的指令,服务器代理通过已经建好的网络连接将该指令发送给远程服 务器, 由远程服务器创建远程进程; 如果远程服务器创建进程失败, 则返回一个失败信 息给服务器代理,服务器代理将会通知 IDE.创建进程失败。如果远程服务器创建进程成 功, 将把所创建的远程进程的信息发回给服务器代理, 服务器代理根据这些信息创建一 个远程进程代理, 该远程进程代理根据远程服务器发回的信息与远程进程建立连接。服 务器代理将远程进程代理对象返回给 IDE, 远程进程代理对象与本地进程对象实现了相 同的 Process接口, IDE可以与使用本地进程一样使用远程进程代理。
远程进程结束的流程如下:
如果远程进程结束, 其父进程, 即远程 server将会收到通知信号。远程 server收到 通知信号后, 向与之连接的远程服务器代理对象发送进程结束事件。远程服务器代理收 到所述进程结束事件后, 根据进程号找到与之对应的远程进程代理对象, 激活等待该进 程结束的线程, 远程进程结束完毕。
IDE主动结束远程进程的流程如下:
IDE向进程代理对象所在的远程服务器代理发送结束进程命令, 远程服务器代理向 与之连接的远程 server发送关掉进程命令,远程 server通过 kill将相应的远程进程关掉。 远程进程关掉后, 远程 server收到通知信号, 远程 server向与之连接的远程服务器代理 发送进程结束事件, 远程 S艮务器代理收到进程结束事件后, 根据进程号找到与之对应的 远程进程代理对象, 激活等待该进程结束的线程, 远程进程结束完毕。
可以看出, 抽象进程模块将远程进程的信息封装起来, IDE在配置好远程服务器的 信息后, 可以象使用本地进程一样使用远程进程, 要运行的进程没有任何限制, 大大方 便了远程编译调试的开发。
本发明实施例二提供一种基于模型驱动进行电信级业务开发的调试装置,所述装置 结构示意图如图 6所示, 该装置包括: 文件同步模块、 抽象进程模块、 解析模块、 调试 控制模块。
所述文件同步模块用于执行同步本地文件与远程文件的操作,所述同步操作可以通 过远程文件镜像、文件时间戳比较等方法来实现, 根据本地和远程文件的改变动态执行 文件同步操作。
所述抽象进程模块与远程服务器相连,可以根据 IDE配置的远程服务器的信息创建 远程服务器代理, 所述远程服务器代理用于与远程服务器建立连接, 与远程服务器进行 信息交互, 并根据远程服务器反馈的远程进程信息创建远程进程代理, 该远程进程代理 根据远程服务器反馈的信息与远程进程建立连接,远程服务器代理将进程代理对象返回 给 IDE, 从而实现进程代理对象与本地进程对象使用相同的进程接口, IDE可以同获取 本地进程一样获取远程进程。 '
所述解析模块用于解析远程编译器和代码调试器的输出信息,判断所述远程编译操 作是否异常, 并解析代码调试器的返回信息。
所述调试控制模块, 用于控制程序文件的调试操作, 使调试过程中代码调试器的控 制信息和运行结果与模型显示和控制命令结合起来, 实现真正的图文调试。
综上所述, 本发明实施例为电信级业务开发工具提供了基于 MDA的调试能力, 实 现了不使用任何模拟器, 达到真正的图文调试。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围并不局限于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到的变化或替 换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保护范围应该以权利要求的保 护范围为准。

Claims

权利要求—
1、 一种基于模型驱动进行电信级业务开发的调试方法, 其特征在于, 在进行调试 操作时, 根据代码反查图元, 使代码调试器的调试信息与模型显示相结合, 实现基于模 型驱动的图文调试。
2、 如权利要求 1所述的一种基于模型驱动进行电信级业务开发的调试方法, 其特 征在于,所述调试操作包括单步操作,所述单步操作进一步包括:单步跳入、单步跳过、 和 /或单步跳出,所述单步跳过操作中需要 ίί定下一个图元的位置,其中确定下一个图元 的方法包括- 集成开发环境 IDE搜索下一步所有可能的图元,在所述图元的入口处设置临时的断 点;
命令代码调试器运行被调试的程序;
确定程序所停止的断点处为下一个图元的位置;
删除所述插入的断点。
3、 如权利要求 1所述的一种基于模型驱动进行电信级业务幵发的调试方法, 其特 征在于,所述调试操作包括单步操作,所述单步操作进一步包括: 单步跳入、单步跳过、 和 /或单步跳出,所述单步跳过操作中需要确定下一个图元的位置,其中确定下一个图元 的方法包括:
在接收到图元单步的命令后,命令代码调试器不断运行单步命令,每次单步停止时, 检查当前代码行所属的图元;
若当前代码属于当前图元, 或不属于任何图元, 则继续执行单步操作;
若当前代码属于另一图元, 则图元单步操作停止。
4、 如权利要求 1所述一种基于模型驱动进行电信级业务开发的调试方法, 其特征 在于, 当处理远程文件时, 所述方法进一步包括:
根据本地与远程文件的改变, 进行动态文件同步处理;
本地 IDE调用远程编译器及远程代码调试器, 编译及调试远程文件;
对所述代码调试器的信息进行解析处理。
5、 如权利要求 4所述一种基于模型驱动进行电信级业务开发的调试方法, 其特征 在于, 所述同步操作的方法包括: 通过远程文件镜像或文件时间戳比较。
6、 如权利要求 1至 5中任一项所述的一种基于模型驱动进行电信级业务开发的调 试方法, 其特征在于, 所述根据代码反査图元的方法进一步包括: 记录每个图元对应的代码的行号, 根据行号反查图元; 或,
在源代码中添加注释信息, 根据所述注释反查图元; 或,
在源代码中插入上报代码, 根据上报代码反査图元。
7、 如权利要求 6所述的一种基于模型驱动进行电信级业务开发的调试方法, 其特 征在于, 所述插入上报代码的方法进一步包括- 在图元出口位置对应的代码处插入上报代码,用于上报信息,集成开发环境 IDE保 存所述信息, 并根据所有上报的信息构造程序运行的轨迹。
8、 如权利要求 7所述的一种基于模型驱动进行电信级业务幵发的调试方法, 其特 征在于, 所述上报的信息包括: 当前图元标识及要走的出口线标识。
9、 如权利要求 7所述的一种基于模型驱动进行电信级业务开发的调试方法, 其特 征在于, 所述上报代码定义为宏的格式。
10、 一种基于模型驱动进行电信级业务开发的调试装置, 其特征在于, 所述装置包 括- 调试控制模块, 用于控制程序文件的调试操作, 根据代码反查图元, 实现代码调试 器的调试信息与模型显示结合起来, 实现基于模型驱动的图文调试。
11、 如权利要求 10所述的一种基于模型驱动进行电信级业务开发的调试装置, 其 特征在于, 所述装置还包括:
文件同步模块, 用于执行本地文件与远程文件的同步操作, 根据本地和远程文件的 改变动态执行文件同步操作;
抽象进程模块, 提供本地进程和远程进程的统一接口, 用于调用本地进程和远程进 程;
解析模块, 用于解析远程编译器和代码调试器的输出信息及代码调试器的返回信 息。
12、 如权利要求 11所述的一种基于模型驱动进行电信级业务开发的调试装置, 其 特征在于, 所述抽象进程模块中进一歩包括:
根据 IDE配置的远程服务器信息创建的远程服务器代理,与远程服务器进行信息交 互, 用于根据远程服务器反馈的远程进程信息创建远程进程代理;
远程服务器代理根据远程服务器反馈的信息创建的远程进程代理,用于根据远程服 务器反馈的信息与远程进程建立连接, 将进程代理对象返回给 IDE, 从而实现进程代理 对象与本地进程对象使用相同的进程接口。
PCT/CN2007/001050 2006-04-24 2007-03-30 Procédé de débogage et appareil pour effectuer un développement de services de classe télécoms guidé par modèle WO2007121658A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP07720624A EP2017983A4 (en) 2006-04-24 2007-03-30 DEBUGGING METHOD AND APPARATUS FOR MAKING MODEL GUIDED TELECOM CLASS SERVICE DEVELOPMENT
CN2007800004212A CN101401333B (zh) 2006-04-24 2007-03-30 一种基于模型驱动进行电信级业务开发的调试方法及装置
US11/970,621 US20080148237A1 (en) 2006-04-24 2008-01-08 Debugging method and apparatus for developing telecom-class service based on model driven

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610076005.8 2006-04-24
CNB2006100760058A CN100485636C (zh) 2006-04-24 2006-04-24 一种基于模型驱动进行电信级业务开发的调试方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/970,621 Continuation US20080148237A1 (en) 2006-04-24 2008-01-08 Debugging method and apparatus for developing telecom-class service based on model driven

Publications (1)

Publication Number Publication Date
WO2007121658A1 true WO2007121658A1 (fr) 2007-11-01

Family

ID=38624545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001050 WO2007121658A1 (fr) 2006-04-24 2007-03-30 Procédé de débogage et appareil pour effectuer un développement de services de classe télécoms guidé par modèle

Country Status (4)

Country Link
US (1) US20080148237A1 (zh)
EP (1) EP2017983A4 (zh)
CN (2) CN100485636C (zh)
WO (1) WO2007121658A1 (zh)

Families Citing this family (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007143278A2 (en) 2006-04-12 2007-12-13 Soft Machines, Inc. Apparatus and method for processing an instruction matrix specifying parallel and dependent operations
WO2008061154A2 (en) 2006-11-14 2008-05-22 Soft Machines, Inc. Apparatus and method for processing instructions in a multi-threaded architecture using context switching
US8458667B2 (en) * 2008-01-30 2013-06-04 National Instruments Corporation Debugging a statechart for a real time target
KR101060181B1 (ko) * 2009-08-03 2011-08-29 강원대학교산학협력단 원격 디버깅을 위한 웹 기반 소프트웨어 디버깅 장치 및 그 방법
CN101916223A (zh) * 2010-08-11 2010-12-15 无锡中星微电子有限公司 程序调试方法及系统
EP3156896B1 (en) 2010-09-17 2020-04-08 Soft Machines, Inc. Single cycle multi-branch prediction including shadow cache for early far branch prediction
CN102567003A (zh) * 2010-12-29 2012-07-11 上海邮电设计咨询研究院有限公司 一种电信增值业务开发环境中的业务调试实现方法
TWI518504B (zh) 2011-03-25 2016-01-21 軟體機器公司 使用可分割引擎實體化的虛擬核心以支援程式碼區塊執行的暫存器檔案節段
WO2012135031A2 (en) 2011-03-25 2012-10-04 Soft Machines, Inc. Executing instruction sequence code blocks by using virtual cores instantiated by partitionable engines
EP2689326B1 (en) 2011-03-25 2022-11-16 Intel Corporation Memory fragments for supporting code block execution by using virtual cores instantiated by partitionable engines
TWI548994B (zh) 2011-05-20 2016-09-11 軟體機器公司 以複數個引擎支援指令序列的執行之互連結構
KR101639853B1 (ko) 2011-05-20 2016-07-14 소프트 머신즈, 인크. 복수의 엔진에 의해 명령어 시퀀스들의 실행을 지원하기 위한 자원들 및 상호접속 구조들의 비집중 할당
KR101832679B1 (ko) 2011-11-22 2018-02-26 소프트 머신즈, 인크. 마이크로프로세서 가속 코드 최적화기
KR101703401B1 (ko) 2011-11-22 2017-02-06 소프트 머신즈, 인크. 다중 엔진 마이크로프로세서용 가속 코드 최적화기
CN102609354A (zh) * 2012-01-19 2012-07-25 北京神州数码思特奇信息技术股份有限公司 一种基于gnu开源软件的c++程序远程调试方法
CN103577315B (zh) * 2012-07-30 2017-02-22 国际商业机器公司 反向调试器和反向调试方法
US9052979B2 (en) * 2012-12-06 2015-06-09 International Business Machines Corporation Program code library searching and selection in a networked computing environment
WO2014150971A1 (en) 2013-03-15 2014-09-25 Soft Machines, Inc. A method for dependency broadcasting through a block organized source view data structure
WO2014150991A1 (en) 2013-03-15 2014-09-25 Soft Machines, Inc. A method for implementing a reduced size register view data structure in a microprocessor
US9891924B2 (en) 2013-03-15 2018-02-13 Intel Corporation Method for implementing a reduced size register view data structure in a microprocessor
US9811342B2 (en) 2013-03-15 2017-11-07 Intel Corporation Method for performing dual dispatch of blocks and half blocks
WO2014150941A1 (en) * 2013-03-15 2014-09-25 Soft Machines, Inc. A method for executing blocks of instructions using a microprocessor architecture having a register view, source view, instruction view, and a plurality of register templates
US9569216B2 (en) 2013-03-15 2017-02-14 Soft Machines, Inc. Method for populating a source view data structure by using register template snapshots
KR20150130510A (ko) 2013-03-15 2015-11-23 소프트 머신즈, 인크. 네이티브 분산된 플래그 아키텍처를 이용하여 게스트 중앙 플래그 아키텍처를 에뮬레이션하는 방법
US9886279B2 (en) 2013-03-15 2018-02-06 Intel Corporation Method for populating and instruction view data structure by using register template snapshots
US10275255B2 (en) 2013-03-15 2019-04-30 Intel Corporation Method for dependency broadcasting through a source organized source view data structure
WO2014150806A1 (en) 2013-03-15 2014-09-25 Soft Machines, Inc. A method for populating register view data structure by using register template snapshots
US9904625B2 (en) 2013-03-15 2018-02-27 Intel Corporation Methods, systems and apparatus for predicting the way of a set associative cache
US10140138B2 (en) 2013-03-15 2018-11-27 Intel Corporation Methods, systems and apparatus for supporting wide and efficient front-end operation with guest-architecture emulation
US9632825B2 (en) 2013-03-15 2017-04-25 Intel Corporation Method and apparatus for efficient scheduling for asymmetrical execution units
CN105210040B (zh) 2013-03-15 2019-04-02 英特尔公司 用于执行分组成块的多线程指令的方法
CN103473173B (zh) * 2013-09-10 2016-03-09 成都品果科技有限公司 一种对iOS系统进行汇编级动态调试的方法及装置
US10289411B2 (en) * 2013-11-18 2019-05-14 Microsoft Technology Licensing, Llc Diagnosing production applications
US9348562B2 (en) 2014-08-25 2016-05-24 International Business Machines Corporation Correcting non-compliant source code in an integrated development environment
CN104679511A (zh) * 2015-02-10 2015-06-03 北京系统工程研究所 基于MDE模型转换的MapReduce代码生成方法
US9983986B2 (en) 2015-09-28 2018-05-29 International Business Machines Corporation Testing code response to injected processing errors
CN107665167B (zh) * 2016-07-28 2021-04-09 华为技术有限公司 程序调试方法、装置及程序开发设备
CN107864411A (zh) * 2017-10-31 2018-03-30 广东小天才科技有限公司 一种视频输出方法及终端设备
CN110502418B (zh) * 2018-05-17 2023-05-23 长沙博为软件技术股份有限公司 一种实现远程调试的方法
CN109144849B (zh) * 2018-07-23 2022-04-01 武汉虹信科技发展有限责任公司 一种嵌入式软件调测方法
US11487643B1 (en) * 2018-11-12 2022-11-01 Xilinx, Inc. Debugging for integrated scripting applications
KR102214698B1 (ko) * 2019-04-05 2021-02-10 주식회사 티맥스 소프트 통합개발환경 상에서 가상 머신 프로그램 및 네이티브 프로그램의 디버깅을 위한 서버 및 컴퓨터 프로그램
CN110554860B (zh) * 2019-06-27 2021-03-12 北京大学 一种软件项目自然语言编程接口nli的构造方法及代码生成方法
CN110659030B (zh) * 2019-09-23 2023-07-14 深圳市众学科技有限公司 Unity项目编译方法、系统、计算机设备及存储介质
CN112860362B (zh) * 2021-02-05 2022-10-04 达而观数据(成都)有限公司 一种机器人自动化流程的可视化调试方法及调试系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4730315A (en) 1984-10-17 1988-03-08 Hitachi, Ltd. Diagrammatic method of testing program
CN1118473A (zh) * 1994-06-30 1996-03-13 坦德姆计算机公司 计算机程序中错误的诊断和改正工具及方法
CN1540517A (zh) * 2003-04-21 2004-10-27 微软公司 Just-My-Code调试技术
CN1601416A (zh) * 2004-10-15 2005-03-30 李迪 一种可重配置的开放式结构计算机数控系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5778230A (en) * 1995-11-13 1998-07-07 Object Technology Licensing Corp. Goal directed object-oriented debugging system
US6393437B1 (en) * 1998-01-27 2002-05-21 Microsoft Corporation Web developer isolation techniques
DE10108487A1 (de) * 2001-02-22 2002-09-12 Giesecke & Devrient Gmbh Verfahren und System zur verteilten Erstellung eines Programms für einen programmierbaren, tragbaren Datenträger
US7849394B2 (en) * 2001-10-25 2010-12-07 The Math Works, Inc. Linked code generation report
US7519960B2 (en) * 2003-12-19 2009-04-14 International Business Machines Corporation Method and system for debugging business process flow

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4730315A (en) 1984-10-17 1988-03-08 Hitachi, Ltd. Diagrammatic method of testing program
CN1118473A (zh) * 1994-06-30 1996-03-13 坦德姆计算机公司 计算机程序中错误的诊断和改正工具及方法
CN1540517A (zh) * 2003-04-21 2004-10-27 微软公司 Just-My-Code调试技术
CN1601416A (zh) * 2004-10-15 2005-03-30 李迪 一种可重配置的开放式结构计算机数控系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2017983A4 *

Also Published As

Publication number Publication date
CN101401333A (zh) 2009-04-01
CN101401333B (zh) 2012-06-27
US20080148237A1 (en) 2008-06-19
CN100485636C (zh) 2009-05-06
EP2017983A1 (en) 2009-01-21
EP2017983A4 (en) 2009-05-20
CN101046766A (zh) 2007-10-03

Similar Documents

Publication Publication Date Title
WO2007121658A1 (fr) Procédé de débogage et appareil pour effectuer un développement de services de classe télécoms guidé par modèle
US20050273757A1 (en) Methods, systems, and computer program products for summarizing operational behavior of a computer program
US7272822B1 (en) Automatically generating software tests based on metadata
US9075919B2 (en) Asynchronous code testing
Cottenier et al. The motorola WEAVR: Model weaving in a large industrial context
US20090144695A1 (en) Method for ensuring consistency during software development
CN103077111B (zh) 一种持续集成失败用例的定位方法及系统
CN108628739A (zh) 一种对Lua脚本进行调试的方法、客户端、服务器及调试器
US8196107B2 (en) Simulating stepping through interpreted code
Marr et al. A concurrency-agnostic protocol for multi-paradigm concurrent debugging tools
CN115757183A (zh) 天熠嵌入式操作系统下一种基于代理的任务级调试方法
Kirchhof et al. Understanding and improving model-driven IoT systems through accompanying digital twins
Zeng et al. Graphical model debugger framework for embedded systems
Adamek et al. Component reliability extensions for fractal component model
López et al. Automatic generation of test models for web services using WSDL and OCL
Franke et al. Androlift: A tool for android application life cycles
WO2007041901A1 (en) System and method for formal verification of statecharts
Pasquier et al. Debugging Paxos in the UML multiverse
CN109348496B (zh) 一种实验室基站故障模拟仿真系统和方法
Schulz Integrating performance tests in a generative software development platform
Alghamdi Queued and Pooled Semantics for State Machines in the Umple Model-Oriented Programming Language
Leroy Behavioral Typing to Support Offline and Online Analysis for Executable DSLs
Wacht et al. A new service description for communication services as basis for automated functional testing
Mattsson et al. Lux: an expect-like test tool written in Erlang: synchronised testing of multiple sessions
Abbors An Approach for Tracing Functional Requirements in Model-Based Testing

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780000421.2

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07720624

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007720624

Country of ref document: EP