CN106598871A - Automatic analysis method and system for collapse file under Linux - Google Patents
Automatic analysis method and system for collapse file under Linux Download PDFInfo
- Publication number
- CN106598871A CN106598871A CN201611243890.4A CN201611243890A CN106598871A CN 106598871 A CN106598871 A CN 106598871A CN 201611243890 A CN201611243890 A CN 201611243890A CN 106598871 A CN106598871 A CN 106598871A
- Authority
- CN
- China
- Prior art keywords
- dump file
- file
- content
- code
- core
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
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/362—Software debugging
- G06F11/366—Software debugging using diagnostics
-
- 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/362—Software debugging
- G06F11/3628—Software debugging of optimised code
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an automatic analysis method and system for a collapse file under Linux. The method comprises the following steps: carrying out compiling by using a preset parameter pair or a c++ source code line to generate a running program prog; setting a detection period of a memory dump file; running the program prog; if the program has an error in running, generating a memory dump file named by 'core. process No.' under a running catalogue, detecting whether the memory dump file exists according to the set detection period, if the memory dump file exists, transferring the memory dump file into a temporary catalogue, analyzing the memory dump file by using a script and a gdb debugging program to locate an error position of the program, and deleting the memory dump file after the analysis is completed; and generating a statistical report by using the script according to a result obtained by the analysis in the step (5). The report generated based on the automatic analysis method can count the number of times when the error occurs and the position of an error code and supply a more powerful support to the priority level for error fixing.
Description
Technical field
The present invention relates to the file automating analysis method of collapse and system under a kind of Linux.
Background technology
The program debugging mode commonly used under linux system has following several：
One, Debugging message is added in program, for the variable of some needs concerns, variate-value journal file, journey is write
Sequence checks journal file, the execution step and result of analysis program after having performed.
Two, using gdb debugging routines, after gdb loading procedures, breakpoint is set, single step performs observation and performs output, or
Person checks implementing result by instructing output variable information after going to breakpoint.
Three, core dump file is produced after program crashing, dump file is debugged by gdb, is checked that code is held
Row order and internal memory stack information, coordinate source code to be analyzed, orientation problem.
The Debugging message that needs are filtered out from substantial amounts of normal, abnormal information is wasted time and energy；Maximum difficulty is debugged in real time
Degree is that the scene that problem occurs is difficult to reduce completely, it is impossible to reappear problem；Dump file is debugged, earlier above two ways
It is more convenient, but it is also required to people and carrys out decision problem point, if while the multiple programs of analysis, relatively complicated.
The content of the invention
The purpose of the present invention is exactly to solve the above problems, there is provided the file automating analysis of collapse under a kind of Linux
Method and system, it passes through gdb instruments and script, and automatically the core dump file that program crashing is produced is analyzed,
Finder collapses code, and can be by the specified cycle to error routine, and errors present is counted, and generates form, no
Need manually to be intervened.The form of generation can be the preferential of modification problem with statistical problem occurrence number, problem code position
Level provides stronger support.
To achieve these goals, the present invention is adopted the following technical scheme that：
A kind of file automating analysis method of collapse under Linux, comprises the steps：
Step (1)：Using predefined parameter to or c++ source code lines compiling generating run program prog；Prog is a mark
Know；
Step (2)：The detection cycle of core dump file is set；
Step (3)：Operation prog programs；
Step (4)：If program operation is problematic, it is " core. process numbers " that a name can be produced under operation catalogue
Core dump file, according to the detection cycle that step (2) sets, detect that core dump file whether there is, if existing just to enter
Enter step (5)；If do not exist being returned to step (4)；
Step (5)：Core dump file is transferred to into temp directory, using script and gdb debugging routines to core dump
File is analyzed, finder Error Location, after analysis terminates, deletes core dump file；
Step (6)：Analysis result out in step (5) is generated into statistical report using script.
The predefined parameter of the step (1) is-g parameters.
The Compilation Method of the step (1) is：G++-g [other specification] [source code file name]；
In the step (5), the memory space that core dump file takes is big, can after the completion of analyzing to internal memory dump file
So that directly core dump file to be deleted, it is also possible to store after being compressed to internal memory dump file, every setting time
Deleting history core dump file, in case manual retrieval；
Step (6) analysis result out includes：It is core dump file generation time, error codes position, identical
Malfunction number of times for position.
The step of step (5) is：
Step (5-1)：Start gdb debugging routines, load the core dump file of " core. process numbers "；
Step (5-2)：Bt instructions, the stack content of display memory dump file are input in gdb debugging routines；
Step (5-3)：Gdb debugging routines are listed stack content and perform code to screen；The stack content with it is described
It is one-to-one to perform between code；
Step (5-4)：Script is parsed to stack content and execution code, extracts analysis result.
The stack content of the step (5-2) includes：Produced variate-value and prog programs during prog program crashings
Execution address.
The analyzing step of the step (5-4) is：
Step (a)：Step (a) includes step (a1) and step (a2)；
Step (a1)：The sentence started with " #0 " is taken out from stack content and execution code；
Step (a2)：Meanwhile, all sentences started with " # " are taken out from stack content and execution code, be recorded as heap
Stack information；
Step (b)：By the sentence taken out in step (a1) with space as decollator, multistage is divided into；
Step (c)：For the segmentation result of step (b)；Record first paragraph content and the 7th section of content；In the first paragraph
Hold for class name：Function name, the 7th section of content are code file name：Line number.
A stack content and perform code sample that the step (5-3) exports：
The content split by space is respectively
Class name function name function entrance address in sequence number memory address code, argument address code file title：Line number.
A kind of collapse file automating analysis system under Linux, including：
Compilation unit, be configured with predefined parameter to or c++ source code lines compiling generating run program prog；
Prog is a mark；
Setting unit, is configured to arrange the detection cycle of core dump file；
Running unit, is configured to run prog programs；
Detector unit, if be configured to, program operation is problematic, and can produce a name under operation catalogue is
The core dump file of " core. process numbers ", according to the detection cycle of setting, detection core dump file whether there is, if depositing
It is being put into analytic unit；
Analytic unit, is configured to for core dump file to be transferred to temp directory, using script and gdb debugging routines pair
Core dump file is analyzed, finder Error Location, after analysis terminates, deletes core dump file；
Signal generating unit, is configured with script analysiss result out and generates statistical report.
The analytic unit, including：
Starting module, is configured to start gdb debugging routines, loads the core dump file of " core. process numbers "；
Display module, is configured to bt instructions are input in gdb debugging routines, in the storehouse of display memory dump file
Hold；
Output module, is configured to gdb debugging routines and lists stack content and perform code to screen；The stack content
It is one-to-one between the execution code；
Parsing module, is configured to script and stack content and execution code is parsed, extract analysis result.
The stack content of the display module includes：Produced variate-value and prog programs during prog program crashings
Perform address.
The parsing module, including：
Sentence extracting sub-module, including：First sentence extracting sub-module and the second sentence extracting sub-module；
First sentence extracting sub-module, is configured to from stack content and execution code take out the language started with " #0 "
Sentence；
Second sentence extracting sub-module, be configured to from stack content and perform code in take out it is all with " # " start
Sentence, is recorded as stack information；
Segmentation submodule, is configured to the sentence of middle taking-up with space as decollator, is divided into multistage；
Record sub module, is configured to for segmentation result；Record first paragraph content and the 7th section of content；The first paragraph
Content is class name：Function name, the 7th section of content are code file name：Line number.
Beneficial effects of the present invention：
1 can catch in time for program bug that non-periodically occurs；
2 without manual intervention；
3 statistical functions provide foundation for code quality analysis.
Description of the drawings
Fig. 1 is operational flow diagram.
Specific embodiment
The invention will be further described with embodiment below in conjunction with the accompanying drawings.
As shown in figure 1, the file automating analysis method of collapse under a kind of Linux, comprises the steps：
1 uses special parameter compiled code, and startup program；
2 startup programs；
3 detect core dump file generated, start gdb instruments and internal memory dump file is analyzed；
After 4 start gdb, input bt instructions show stack content；
#0 0x001d2a40in CFigureMenuItemBase::Draw (this=0x5f4fd50, bSel=-
1093630660)at MenuItem.cpp:138
The content split by space is respectively
Class name function name function entrance address in sequence number memory address code, argument address code file title：Line number
5 from stack content analysis obtain required content write statistical report.
Although the above-mentioned accompanying drawing that combines is described to the specific embodiment of the present invention, not to present invention protection model
The restriction enclosed, one of ordinary skill in the art should be understood that on the basis of technical scheme those skilled in the art are not
The various modifications made by needing to pay creative work or deformation are still within protection scope of the present invention.
Claims (10)
1. the file automating analysis method of collapse under a kind of Linux, is characterized in that, comprise the steps：
Step (1)：Using predefined parameter to or c++ source code lines compiling generating run program prog；Prog is a mark；
Step (2)：The detection cycle of core dump file is set；
Step (3)：Operation prog programs；
Step (4)：If program operation is problematic, a name can be produced under operation catalogue for the interior of " core. process numbers "
Dump file is deposited, according to the detection cycle that step (2) sets, detects that core dump file whether there is, if exist being put into step
Suddenly (5)；If do not exist being returned to step (4)；
Step (5)：Core dump file is transferred to into temp directory, using script and gdb debugging routines to internal memory dump file
It is analyzed, finder Error Location, after analysis terminates, deletes core dump file；
Step (6)：Analysis result out in step (5) is generated into statistical report using script.
2. the file automating analysis method of collapse under a kind of Linux as claimed in claim 1, is characterized in that,
In the step (5), the memory space that core dump file takes is big, can be straight after the completion of analyzing to internal memory dump file
Connect and core dump file is deleted, it is also possible to store after being compressed to internal memory dump file, delete every setting time
History core dump file, in case manual retrieval.
3. the file automating analysis method of collapse under a kind of Linux as claimed in claim 1, is characterized in that,
Step (6) analysis result out includes：Core dump file generation time, error codes position, same position
Error number of times.
4. the file automating analysis method of collapse under a kind of Linux as claimed in claim 1, is characterized in that,
The step of step (5) is：
Step (5-1)：Start gdb debugging routines, load the core dump file of " core. process numbers "；
Step (5-2)：Bt instructions, the stack content of display memory dump file are input in gdb debugging routines；
Step (5-3)：Gdb debugging routines are listed stack content and perform code to screen；The stack content and the execution
It is one-to-one between code；
Step (5-4)：Script is parsed to stack content and execution code, extracts analysis result.
5. the file automating analysis method of collapse under a kind of Linux as claimed in claim 4, is characterized in that,
The stack content of the step (5-2) includes：During prog program crashings, produced variate-value and prog programs holds
Row address.
6. the file automating analysis method of collapse under a kind of Linux as claimed in claim 4, is characterized in that,
The analyzing step of the step (5-4) is：
Step (a)：Step (a) includes step (a1) and step (a2)；
Step (a1)：The sentence started with " #0 " is taken out from stack content and execution code；
Step (a2)：Meanwhile, all sentences started with " # " are taken out from stack content and execution code, be recorded as storehouse letter
Breath；
Step (b)：By the sentence taken out in step (a1) with space as decollator, multistage is divided into；
Step (c)：For the segmentation result of step (b)；Record first paragraph content and the 7th section of content；The first paragraph content is
Class name：Function name, the 7th section of content are code file name：Line number.
7. the file automating analysis method of collapse under a kind of Linux as claimed in claim 4, is characterized in that,
A stack content and perform code sample that the step (5-3) exports：
The content split by space is respectively
Class name function name function entrance address in sequence number memory address code, argument address code file title：Line number.
8. the file automating analysis system of collapse under a kind of Linux, is characterized in that, including：
Compilation unit, be configured with predefined parameter to or c++ source code lines compiling generating run program prog；Prog is
Individual mark；
Setting unit, is configured to arrange the detection cycle of core dump file；
Running unit, is configured to run prog programs；
Detector unit, if be configured to, program operation is problematic, and it is that " core. enters that a name can be produced under operation catalogue
The core dump file of journey number ", according to the detection cycle of setting, detection core dump file whether there is, if exist being put into
Analytic unit；
Analytic unit, is configured to for core dump file to be transferred to temp directory, using script and gdb debugging routines to internal memory
Dump file is analyzed, finder Error Location, after analysis terminates, deletes core dump file；
Signal generating unit, is configured with script analysiss result out and generates statistical report.
9. system as claimed in claim 8, is characterized in that, the analytic unit, including：
Starting module, is configured to start gdb debugging routines, loads the core dump file of " core. process numbers "；
Display module, is configured to bt instructions, the stack content of display memory dump file are input in gdb debugging routines；
Output module, is configured to gdb debugging routines and lists stack content and perform code to screen；The stack content and institute
It is one-to-one to state between execution code；
Parsing module, is configured to script and stack content and execution code is parsed, extract analysis result.
10. system as claimed in claim 9, is characterized in that, the parsing module, including：
Sentence extracting sub-module, including：First sentence extracting sub-module and the second sentence extracting sub-module；
First sentence extracting sub-module, is configured to from stack content and execution code take out the sentence started with " #0 "；
Second sentence extracting sub-module, is configured to take out all sentences started with " # " from stack content and execution code,
It is recorded as stack information；
Segmentation submodule, is configured to the sentence of middle taking-up with space as decollator, is divided into multistage；
Record sub module, is configured to for segmentation result；Record first paragraph content and the 7th section of content；The first paragraph content
For class name：Function name, the 7th section of content are code file name：Line number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611243890.4A CN106598871A (en) | 2016-12-29 | 2016-12-29 | Automatic analysis method and system for collapse file under Linux |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611243890.4A CN106598871A (en) | 2016-12-29 | 2016-12-29 | Automatic analysis method and system for collapse file under Linux |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106598871A true CN106598871A (en) | 2017-04-26 |
Family
ID=58604965
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611243890.4A Pending CN106598871A (en) | 2016-12-29 | 2016-12-29 | Automatic analysis method and system for collapse file under Linux |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106598871A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108089977A (en) * | 2017-11-28 | 2018-05-29 | 维沃移动通信有限公司 | A kind of abnormality eliminating method of application program, device and mobile terminal |
| CN108549600A (en) * | 2018-03-29 | 2018-09-18 | 珠海市魅族科技有限公司 | A kind of method for analyzing performance and device, server and readable storage medium storing program for executing |
| CN108664250A (en) * | 2018-03-27 | 2018-10-16 | 北京奇艺世纪科技有限公司 | A kind of code process method and device |
| CN108958993A (en) * | 2017-05-18 | 2018-12-07 | 兰州大学 | A kind of online internal memory detector MEMDOG based on Linux |
| CN110096888A (en) * | 2019-04-18 | 2019-08-06 | 苏州浪潮智能科技有限公司 | A kind of method and system for accelerating verifying and analysis SMM security risk |
| CN110147294A (en) * | 2019-05-23 | 2019-08-20 | Oppo广东移动通信有限公司 | Acquisition methods, device, terminal and the computer readable storage medium of Debugging message |
| CN110262918A (en) * | 2019-06-19 | 2019-09-20 | 深圳市网心科技有限公司 | Process collapses analysis method and device, distributed apparatus and storage medium |
| CN111459933A (en) * | 2020-03-12 | 2020-07-28 | 平安科技（深圳）有限公司 | GDB data dynamic expansion method, device and storage medium |
| CN112416733A (en) * | 2019-08-20 | 2021-02-26 | 深圳市优必选科技股份有限公司 | Memory detection method, memory detection device and intelligent equipment |
| CN112965892A (en) * | 2019-12-12 | 2021-06-15 | 大唐移动通信设备有限公司 | Abnormal information acquisition method and device for software system, electronic equipment and medium |
| CN113127248A (en) * | 2021-04-02 | 2021-07-16 | 清华大学 | Automatic crash recovery method and system for ROS program of robot |
| WO2022068001A1 (en) * | 2020-09-29 | 2022-04-07 | 苏州亿歌网络科技有限公司 | Gdb-based lua debugging method and device, apparatus, and storage medium |
| WO2022259161A1 (en) * | 2021-06-10 | 2022-12-15 | International Business Machines Corporation | Self-optimizing analysis system for core dumps |
| CN115858366A (en) * | 2022-12-13 | 2023-03-28 | 北京水木羽林科技有限公司 | Grammar generation-based database automatic test method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1704908A (en) * | 2004-05-26 | 2005-12-07 | 华为技术有限公司 | Method for locating program abnormity |
| US20070168980A1 (en) * | 2006-01-06 | 2007-07-19 | Reed David C | Apparatus and method to debug a software program |
| CN103150226A (en) * | 2013-04-01 | 2013-06-12 | 山东鲁能软件技术有限公司 | Abnormal dump and recovery system for computer model and dump and recovery method thereof |
| CN104536874A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client collapse locating method and device |
-
2016
- 2016-12-29 CN CN201611243890.4A patent/CN106598871A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1704908A (en) * | 2004-05-26 | 2005-12-07 | 华为技术有限公司 | Method for locating program abnormity |
| US20070168980A1 (en) * | 2006-01-06 | 2007-07-19 | Reed David C | Apparatus and method to debug a software program |
| CN103150226A (en) * | 2013-04-01 | 2013-06-12 | 山东鲁能软件技术有限公司 | Abnormal dump and recovery system for computer model and dump and recovery method thereof |
| CN104536874A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client collapse locating method and device |
Non-Patent Citations (1)
| Title |
|---|
| ENWINFWD: "利用内存转储文件进行程序调试——gdb入门之一", 《HTTP://BLOG.CHINAUNIX.NET/UID-12555930-ID-2929690.HTML》 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958993A (en) * | 2017-05-18 | 2018-12-07 | 兰州大学 | A kind of online internal memory detector MEMDOG based on Linux |
| CN108958993B (en) * | 2017-05-18 | 2021-11-19 | 兰州大学 | Linux-based online memory detector MEMDOG |
| CN108089977A (en) * | 2017-11-28 | 2018-05-29 | 维沃移动通信有限公司 | A kind of abnormality eliminating method of application program, device and mobile terminal |
| CN108664250A (en) * | 2018-03-27 | 2018-10-16 | 北京奇艺世纪科技有限公司 | A kind of code process method and device |
| CN108549600A (en) * | 2018-03-29 | 2018-09-18 | 珠海市魅族科技有限公司 | A kind of method for analyzing performance and device, server and readable storage medium storing program for executing |
| CN110096888A (en) * | 2019-04-18 | 2019-08-06 | 苏州浪潮智能科技有限公司 | A kind of method and system for accelerating verifying and analysis SMM security risk |
| CN110147294A (en) * | 2019-05-23 | 2019-08-20 | Oppo广东移动通信有限公司 | Acquisition methods, device, terminal and the computer readable storage medium of Debugging message |
| CN110147294B (en) * | 2019-05-23 | 2023-10-03 | Oppo广东移动通信有限公司 | Method and device for acquiring debugging information, terminal and computer readable storage medium |
| CN110262918A (en) * | 2019-06-19 | 2019-09-20 | 深圳市网心科技有限公司 | Process collapses analysis method and device, distributed apparatus and storage medium |
| CN112416733B (en) * | 2019-08-20 | 2023-12-29 | 深圳市优必选科技股份有限公司 | Memory detection method, memory detection device and intelligent device |
| CN112416733A (en) * | 2019-08-20 | 2021-02-26 | 深圳市优必选科技股份有限公司 | Memory detection method, memory detection device and intelligent equipment |
| CN112965892A (en) * | 2019-12-12 | 2021-06-15 | 大唐移动通信设备有限公司 | Abnormal information acquisition method and device for software system, electronic equipment and medium |
| CN111459933B (en) * | 2020-03-12 | 2023-06-06 | 平安科技（深圳）有限公司 | GDB data dynamic expansion method, device and storage medium |
| CN111459933A (en) * | 2020-03-12 | 2020-07-28 | 平安科技（深圳）有限公司 | GDB data dynamic expansion method, device and storage medium |
| WO2022068001A1 (en) * | 2020-09-29 | 2022-04-07 | 苏州亿歌网络科技有限公司 | Gdb-based lua debugging method and device, apparatus, and storage medium |
| CN113127248A (en) * | 2021-04-02 | 2021-07-16 | 清华大学 | Automatic crash recovery method and system for ROS program of robot |
| WO2022259161A1 (en) * | 2021-06-10 | 2022-12-15 | International Business Machines Corporation | Self-optimizing analysis system for core dumps |
| US11841788B2 (en) | 2021-06-10 | 2023-12-12 | International Business Machines Corporation | Self-optimizing analysis system for core dumps |
| CN115858366A (en) * | 2022-12-13 | 2023-03-28 | 北京水木羽林科技有限公司 | Grammar generation-based database automatic test method and system |
| CN115858366B (en) * | 2022-12-13 | 2024-03-29 | 北京水木羽林科技有限公司 | Automatic database testing method and system based on grammar generation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106598871A (en) | Automatic analysis method and system for collapse file under Linux | |
| CN110764753A (en) | Business logic code generation method, device, equipment and storage medium | |
| US20020091968A1 (en) | Object-oriented data driven software GUI automated test harness | |
| US20060271830A1 (en) | Auto-executing tool for developing test harness files | |
| US7702958B2 (en) | Auto-recording tool for developing test harness files | |
| JPH02272645A (en) | Method for supporting program debugging | |
| CN104778124A (en) | Automatic testing method for software application | |
| CN101944059A (en) | Automatic analysis method and device of crash information of computer software | |
| CN101996131A (en) | Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word | |
| CN103425574A (en) | Method and device for testing applications | |
| US20070061641A1 (en) | Apparatus and method for generating test driver | |
| CN102231109A (en) | Traceless manageable automatic source code instrumentation method | |
| CN102508775A (en) | Interactive automation test system | |
| CN103605556A (en) | Virtual test subject integrally-constructing system and method | |
| CN102479152A (en) | Method and device for obtaining tool automatic test results on basis of Android platform | |
| CN101604290B (en) | Background module test method and backstage module test system | |
| CN103678116A (en) | Method and system for facilitating automated program testing | |
| US8381185B2 (en) | Apparatus, system, and method for dynamic module flow analysis | |
| CN103186459B (en) | JAVA graphic user interface automatic test approach based on script | |
| CN104765635A (en) | Method and system for checking multiple languages in APK | |
| CN109857637A (en) | A kind of Java language method coverage rate and method input and output statistical method and device based on note | |
| CN102063367B (en) | Off-line analysis method and device aiming at computer crash program | |
| CN105677569B (en) | Android automated test tools and method of testing based on event handler | |
| CN106598843B (en) | A kind of software log behavior automatic identifying method based on program analysis | |
| CN110286882B (en) | Foreground system design and verification method based on model detection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 250101 block B, Yinhe building, 2008 Xinjie street, hi tech Zone, Ji'nan, Shandong. Applicant after: Shandong Luneng Intelligent Technology Co., Ltd. Address before: 250101 B block 626, Yinhe building, 2008 Xinjie street, Ji'nan high tech Zone, Shandong. Applicant before: Shandong Luneng Intelligent Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170426 |
|
| RJ01 | Rejection of invention patent application after publication |