CN101719090A - Method for automatically analyzing crash cause of computer software system - Google Patents
Method for automatically analyzing crash cause of computer software system Download PDFInfo
- Publication number
- CN101719090A CN101719090A CN200910214346A CN200910214346A CN101719090A CN 101719090 A CN101719090 A CN 101719090A CN 200910214346 A CN200910214346 A CN 200910214346A CN 200910214346 A CN200910214346 A CN 200910214346A CN 101719090 A CN101719090 A CN 101719090A
- Authority
- CN
- China
- Prior art keywords
- function
- collapse
- module
- crash
- computer software
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a method for automatically analyzing the crash cause of a computer software system. The method for automatically analyzing the crash cause of the computer software system comprises the following steps of: a. opening a crash dump file; b. respectively searching stack information of each thread of each processor, searching a user-mode abnormal error triggering function for a user-mode crash dump file, and searching a kernel-mode abnormal error triggering function for a kernel-mode crash dump file; c. checking a previous calling function at the abnormal error occurrence time according to the searched abnormal error triggering functions, temporarily setting the calling function to be a crash function if the calling function is an effective function name, and temporarily setting a module attached to the calling function to be a crash module; and d. acquiring crash information according to the acquired crash function and the acquired crash module, and storing the crash information into a database. The invention has the advantage that the automatic analysis to the crash cause of the software system can be realized.
Description
Technical field
The present invention relates to the computer software area of maintenance, relate in particular to a kind of method that crash cause of computer software system is analyzed automatically.
Background technology
The software systems of computing machine are in operational process; can produce unusual because of various X factors; finally cause application crash or operating system blue screen; the collapse analytical technology is meant; the crashdump file (dump) that generates after operation makes mistakes to software systems is analyzed and is added up; and it is capable therefrom to find out the address and the correlative code thereof that collapse when taking place, thereby provides believable foundation for solving the software systems fault.At present most ofs known collapses analyze the collection that only realized the collapse file and abnormity point statistics (utilization be the software systems collapse time unusual pointer realization), and all do not provide analytic function at the later kernel state crashdump file of system's blue screen.
Summary of the invention
The objective of the invention is to overcome deficiency of the prior art, a kind of method that crash cause of computer software system is analyzed automatically is provided, use this method to analyze crashdump file automatically, and obtain collapse function and collapse module, and then know multinomial concrete crash info, be convenient to statistics to various different crash infos.
To achieve these goals, by the following technical solutions:
To the method that crash cause of computer software system is analyzed automatically, it comprises the steps:
A, open crashdump file;
B, retrieve the stack information of each each thread of processor respectively, user's attitude of exception error seek to(for) user's attitude crashdump file triggers function; The kernel state of exception error seek to(for) the kernel state crashdump file triggers function;
The exception error that c, basis search triggers function, check the unusual last call function constantly that takes place, if this call function is an efficient function name, then fix tentatively this call function and be the collapse function, tentative the module that this call function is subordinate to for collapsing module;
D, obtain crash info, and crash info is stored to database according to collapse function that obtains and collapse module.
Further technical scheme is,
Between step a and step b, also comprise step a1:
A1, carry out unique name to crashdump file.
Further technical scheme is again,
Between step a1 and step b, also comprise step a2:
A2, loading debug symbol file.
The debug mechanism that said method utilizes Windows operating system to provide, internal storage data when automatically the collapse of preserving in the crashdump file being taken place is analyzed, and recall and the module information that loads when function call sequence, register value, collapse take place, address information and the related system thereof that collapse takes place, therefrom find out the reason that causes collapsing generation, can provide believable foundation for follow-up software fault analysis and software quality estimation.The major advantage of the inventive method is:
1, based on Windows debugging technique technology, the series of analysis process automation, and accept or reject automatically according to analysis result, intelligence is chosen the analysis operation order, effectively solved the collapse dump analyze in to the too high problem of operating personnel's technical requirement.
2, support a series of collapse analysis rule,, use different rules to analyze according to different collapse flow processs.
3, support analysis at the later kernel state crashdump file of system's blue screen can directly navigate to concrete collapse function, code line number, the on-the-spot contents such as stacked data of collapse.
Embodiment
The principle of method of the present invention is based on the Windows debugging technique and debugs API accordingly.The Windows debugging technique is built in the operating system nucleus the inside, and a series of Windows API and assembly bag externally are provided.The Windows debug engine that assembly bag Debugging Tools for Windows (hereinafter to be referred as the WinDBG) the inside that the present invention has utilized the Windows debugging technique to provide provides is analyzed automatically to crashdump file.The inventive method itself to as if crashdump file.The generation method of crashdump file mainly contains following:
● Windows error reporting mechanism
●MiniDumpWriteDump?Windows?API
● read the internal memory of collapse process
● the application program debugger
Utilize said method to generate after the crashdump file, just can utilize the method for introducing below to collapse the analytic process of dump.
To the method that crash cause of computer software system is analyzed automatically, it comprises the steps:
A, open crashdump file, check the legitimacy and the validity of file;
A1, carry out unique name so that the management of subsequent file to crashdump file;
A2, loading debug symbol file; The debug symbol file is the bridge that the binary message of debugged program and source program code are connected, and has write down information such as variable, type, function definition, source code lines in the debug symbol file.
Software runtime environment constantly takes place in a3, inspection collapse, for the x64 system, if operate under the WoW64 environment, then carries out 32-64 running environment and switches, otherwise do not carry out the environment switching.
B, retrieve the stack information of each each thread of processor respectively, user's attitude of exception error seek to(for) user's attitude crashdump file triggers function; The kernel state of exception error seek to(for) the kernel state crashdump file triggers function; If do not find exception error to trigger function, jump to step c2.
The exception error that c, basis search triggers function, check the unusual last call function constantly that takes place, if this call function is an efficient function name, then fix tentatively this call function and be the collapse function, tentative the module that this call function is subordinate to for collapsing module;
If collapse module that c1 step c finds or collapse function belong to the trusted module tabulation, that continue to check so that the exception error that searches among the step b triggers that thread takes place the collapse of function place goes up a call function again, module up to call function that is checked through and place thereof is non-trusted module, this function that is checked through at last is decided to be the collapse function, and the module that this collapse function is subordinate to is designated as the collapse module.Comprise a plurality of trusted module in the said trusted module tabulation, these trusted module are meant that the programming personnel thinks that can be defined as can not be the module that causes system crash; If this process does not find the collapse function after finishing, forward step c3 to; If find the collapse function, enter steps d.
C2, obtain breakdown address, exception error code according to the value of register, then according to breakdown address, the API and the order that utilize the Windows debug engine to provide are carried out the analysis of original call stack to crashdump file, obtain a nearest collapse module and a nearest call function, and a nearest call function is designated as the collapse function, the module that this function is subordinate to is designated as the collapse module; If this process does not find the collapse function after finishing, forward step c3 to; If find the collapse function, enter steps d.
C3, the breakdown address in collapse time is carried out dis-assembling, check whether there is the information that can identify the collapse function,, forward step c4 to if this process does not find the collapse function after finishing; If find the collapse function, enter steps d.
C4, will collapse function so and be recorded as the state that do not find, the collapse module will be recorded as the unusual module that takes place under the thread constantly.
D, obtain crash info, and crash info is stored to database according to collapse function that obtains and collapse module.
It is as follows that the exception error of known users attitude collapse at present triggers function, and can constantly change according to the renewal of operating system:
The UnhandledExceptionFilter function that kernel32.dll provides, the FatalAppExitW function that kernel32.dll provides, the FatalAppExitA function that kernel32.dll provides, the RaiseException function that kernel32.dll provides, the RaiseException function that kernelbase.dll provides, the NtRaiseHardError function that ntdll.dll provides, the NtRaiseException function that ntdll.dll provides, the KiUserExceptionDispatcher function that ntdll.dll provides, the CxxThrowException function, the TppExceptionFilter function that ntdll.dll provides, the TppWorkerpInnerExceptionFilter function that ntdll.dll provides, the except_handler function, the except_handler2 function, the except_handler3 function, the report_failure function.
It is as follows that the collapse of the exception error of present known kernel state triggers function, and can constantly change according to the renewal of operating system:
The KeBugCheck that the Windows kernel provides, KeBugCheckEx, KeBugCheckEx2, KiTrap, DbgBreakPoint, DbgUserBreakPoint, ExpRaiseHardError, ExpSystemErrorHandler, PoShutdownBugcheck, KeBugCheck, KiBugCheck function.
Crash info described in the steps d comprises at least a in the following message;
1) collapse time of origin;
2) operating system;
3) processor number and type;
4) collapse context process name;
5) avalanche mode block name;
6) abnormality code and abnormal cause;
7) Beng Kui instruction address and module offset address;
8) collapse module routing information;
9) information that avalanche mode block file version information, product version information etc. can the identification document attributes;
Each thread stacks information when 10) collapse takes place;
11) register information;
12) and other help to collapse the information of statistics.
Wherein, the 1st) crash info can obtain from crashdump file-3), and other crash infos then need could obtain after obtaining collapse function and collapse module.
The detailed process of above-mentioned steps c2 is, utilizes debug engine order and API, obtains the stack address that the EBP register of collapse thread points to, and utilizes debug engine order and API to enumerate original call stack information then, draws shape such as following tabulation:
0239ff08 0239ff48
0239fef8 75e79a26 kernel32！HeapFree+0x14
0239ff10 01f40000
0239ff14 00000000
0239ff18 01ae4c08 kavevent+0x4c08
0239ff1c 582b040a
0239ff20 01af2868 kavevent+0x12868
0239ff24 01f425a8
0239ff28 0239ff80
0239ff2c 00000000
0239ff30 00000000
0239ff34 00000000
0239ff38 01ae5a53 kavevent+0x5a53
0239ff3c 0239ff70
HeapFree+0x14),, check then whether this module is trusted module, if then continue to check next line if having.If not trusted module, a module that finds is so at first collapsed module exactly, and the offset address of this module is exactly a breakdown address.
Carry out the example explanation at kernel state roll-off file and user's attitude dump file respectively below.
Kernel state:
We can check callstack the inside similar nt! The function of the KeBugCheck exception error of the kernel state (trigger function), below for example nt! KeBugCheckEx, if find that this function is arranged, we can check down that storehouse calls so,
00 ae9c01d8 8054c583 000000c2 00000007 00000cd4nt！KeBugCheckEx+0x1b
01 ae9c0228 ba623392 e39c8428 00000000 00000000nt！ExFreePoolWithTag+0x2a3
02 ae9c0244 ba6230f8 e3a89008 c0000001 ae9c0268kavpm！DeleteProcessObject+0x52[e:\build\src\kavprocessm.c@1416]
03 ae9c0254 ba623aa0 e3a89008 e3a89008 01000064kavpm！KxEReleaseProcessObject+0x58
[e:\build\src\kavprocessm.c@1308]
04 ae9c0268 ba623d96 00000d90 00000000 00000001kavpm！KxERemoveProcessObject+0xb0
[e:\build\src\kavprocessm.c@1791]
05 ae9c02b0 ba7481b1 00000d90 00000db0 ba752e00kavpm！KxECreateProcessNotifyRoutine+0x276
[e:\build\src\kavprocessm.c@1953]
06 ae9c02c8 805d2b60 00000d90 00000db0 00000000kavuty！StubCreateProcessNotifyRoutine+0x61
[e:\build\build\src\kavutynr.c@50]
07 ae9c02ec?805d3672 00000001 00000008 87ff7cd0nt！PspExitProcess+0x5e
Above for example the 00th row, triggered abnormal function nt! KeBugCheckEx, our storehouse that can retrieve the back calls so, because the nt module belongs to trusted module, so 01 row is left in the basket, when checking 02 row, kavpm belongs to non-trusted module, so kavpm done the collapse module by note, and the DeleteProcessObject function of kavpm the inside is done the collapse function by note. DeleteProcessObject+0x52.Corresponding specific code is capable be e: build src the 1416th line code of kavprocessm.c file.Nt is the abbreviation of nt kernel, may be different filenames such as ntosktrnl.exe, ntkrnlmp.exe below different environment.
In kernel state the inside, except common abnormal erroneous trigger functions such as common KeBugCheck, KeBugCheckEx, KeBugCheckEx2, KiTrap, also have similarly some distortion, for example KiTrap00 etc.
User's attitude:
RaiseException is that exception error triggers function, and what call RaiseException also is that an exception error in the tabulation the inside triggers function _ CxxThrowException.When we enumerate, can filter out 00 row and 01 row, find that then 02 row is that kastraydll is not a trusted module, therefore note is done the collapse module, because the collapse module lacks symbol file, therefore can't mapping function name and code line, can only provide the offset address kastraydll+0x2acd7 of collapse
00 016c56e8 01548e69 e06d7363 00000001 00000003kernel32！RaiseException+0x53
01 016c5720 0144acd7 016c5734 0145bad4 01435c2amsvcr80_1520000！_CxxThrowException+0x46
[f:\sp\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp@161]
02 016c572c 01435c2a 8007000e 01435c64 00000000kastraydll+0x2acd7
03 016c5730 8007000e 01435c64 00000000 016c577ckastraydll+0x15c2a
04 016c5734?01435c64?00000000?016c577c?016cfddc?0x8007000e
05 016c5738 00000000 016c577c 016cfddc 01466758kastraydll+0x15c64
Above embodiment is the unrestricted technical scheme of the present invention in order to explanation only.Any modification or partial replacement that does not break away from spirit and scope of the invention should be encompassed in the middle of the claim scope of the present invention.
Claims (12)
1. the method that crash cause of computer software system is analyzed automatically is characterized in that, comprises the steps:
A, open crashdump file;
B, retrieve the stack information of each each thread of processor respectively, user's attitude of exception error seek to(for) user's attitude crashdump file triggers function; The kernel state of exception error seek to(for) the kernel state crashdump file triggers function;
The exception error that c, basis search triggers function, check the unusual last call function constantly that takes place, if this call function is an efficient function name, then fix tentatively this call function and be the collapse function, tentative the module that this call function is subordinate to for collapsing module;
D, obtain crash info, and crash info is stored to database according to collapse function that obtains and collapse module.
2. the method that crash cause of computer software system is analyzed automatically according to claim 1, it is characterized in that described user's attitude exception error triggers function and comprises: the UnhandledExceptionFilter function that kernel32.dll provides, the FatalAppExitW function that kernel32.dll provides, the FatalAppExitA function that kernel32.dll provides, the RaiseException function that kernel32.dll provides, the RaiseException function that kernelbase.dll provides, the NtRaiseHardError function that ntdll.dll provides, the NtRaiseException function that ntdll.dll provides, the KiUserExceptionDispatcher function that ntdll.dll provides, the CxxThrowException function, the TppExceptionFilter function that ntdll.dll provides, the TppWorkerpInnerExceptionFilter function that ntdll.dll provides, the except_handler function, the except_handler2 function, the except_handler3 function, the report_failure function.
3. the method that crash cause of computer software system is analyzed automatically according to claim 1, it is characterized in that described kernel state exception error triggers function and comprises: the KeBugCheck that the Windows kernel provides, KeBugCheckEx, KeBugCheckEx2, KiTrap, DbgBreakPoint, DbgUserBreakPoint, ExpRaiseHardError, ExpSystemErrorHandler, PoShutdownBugcheck, KeBugCheck, KiBugCheck function.
4. according to any described method that crash cause of computer software system is analyzed automatically in the claim 1 to 3, it is characterized in that, between step a and step b, also comprise step a1:
A1, carry out unique name to crashdump file.
5. the method that crash cause of computer software system is analyzed automatically according to claim 4 is characterized in that, also comprises step a2 between step a1 and step b:
A2, loading debug symbol file.
6. the method that crash cause of computer software system is analyzed automatically according to claim 5 is characterized in that, also comprises step a3 between step a2 and step b:
Software runtime environment constantly takes place in a3, inspection collapse, for the x64 system, if operate under the WoW64 environment, then carries out 32-64 running environment and switches, otherwise do not carry out the environment switching.
7. the method that crash cause of computer software system is analyzed automatically according to claim 6 is characterized in that, also comprises step c1 between step c and steps d:
If collapse module that c1 step c finds or collapse function belong to the trusted module tabulation, that continue to check so that the exception error that searches among the step b triggers that thread takes place the collapse of function place goes up a call function again, module up to call function that is checked through and place thereof is non-trusted module, this function that is checked through at last is decided to be the collapse function, and the module that this collapse function is subordinate to is designated as the collapse module.
8. according to any described method that crash cause of computer software system is analyzed automatically in the claim 1 to 3, it is characterized in that, between step c and steps d, also comprise step c2:
If c2 does not find exception error to trigger function, then the value according to register obtains breakdown address, exception error code, then according to breakdown address, the API and the order that utilize the Windows debug engine to provide are carried out the analysis of original call stack to crashdump file, obtain a nearest collapse module and a nearest call function, and a nearest call function is designated as the collapse function, the module that this function is subordinate to is designated as the collapse module.
9. the method that crash cause of computer software system is analyzed automatically according to claim 8 is characterized in that, also comprises step c3 between step c2 and steps d:
If do not find the collapse function among the c3 step c2, the breakdown address in the time of then to collapse is carried out dis-assembling, checks whether there is the information that can identify the collapse function.
10. the method that crash cause of computer software system is analyzed automatically according to claim 9 is characterized in that, also comprises step c4 between step c3 and steps d:
If c4 step c3 does not also find the collapse function, will collapse function so and be recorded as the state that do not find, the collapse module is recorded as the unusual affiliated module of thread constantly that takes place.
11. the method that crash cause of computer software system is analyzed automatically according to claim 7 is characterized in that, also comprises step c5 between step c1 and steps d:
If do not find the collapse function among the C5 step c1, the breakdown address in the time of then to collapse is carried out dis-assembling, checks whether there is the information that can identify the collapse function.
12., it is characterized in that crash info described in the steps d comprises at least a in the following message according to claim 1 or the 2 or 3 described methods that crash cause of computer software system is analyzed automatically;
1) collapse time of origin;
2) collapse context process name;
3) avalanche mode block name;
4) operating system;
5) processor number and type;
6) abnormality code and abnormal cause;
7) Beng Kui instruction address and module offset address;
8) collapse module routing information;
9) information that avalanche mode block file version information, product version information etc. can the identification document attributes;
Each thread stacks information when 10) collapse takes place;
11) register information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910214346A CN101719090A (en) | 2009-12-25 | 2009-12-25 | Method for automatically analyzing crash cause of computer software system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910214346A CN101719090A (en) | 2009-12-25 | 2009-12-25 | Method for automatically analyzing crash cause of computer software system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101719090A true CN101719090A (en) | 2010-06-02 |
Family
ID=42433668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910214346A Pending CN101719090A (en) | 2009-12-25 | 2009-12-25 | Method for automatically analyzing crash cause of computer software system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101719090A (en) |
Cited By (46)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101944059A (en) * | 2010-08-20 | 2011-01-12 | 北京神州泰岳软件股份有限公司 | Automatic analysis method and device of crash information of computer software |
| CN102768639A (en) * | 2012-06-11 | 2012-11-07 | 北京奇虎科技有限公司 | Operating system kernel-level error positioning method and device |
| CN102929761A (en) * | 2012-11-16 | 2013-02-13 | 赛尔网络有限公司 | System and method for responding corruption error |
| CN103106132A (en) * | 2013-03-05 | 2013-05-15 | 中标软件有限公司 | Kernel function calling stack analyzing and debugging method in case of Linux system breakdown |
| CN103226510A (en) * | 2013-04-27 | 2013-07-31 | 华为技术有限公司 | Method and device for analyzing vmcore file |
| CN103309762A (en) * | 2013-06-21 | 2013-09-18 | 杭州华三通信技术有限公司 | Equipment exception handling method and device |
| CN103399803A (en) * | 2013-07-29 | 2013-11-20 | 北京小米科技有限责任公司 | Method and device for collecting browser breakdown information and terminal equipment |
| CN103678109A (en) * | 2012-09-25 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Dump document analysis method, device and system |
| WO2014169678A1 (en) * | 2013-04-15 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Method and device for signing program crash |
| CN104142885A (en) * | 2013-05-09 | 2014-11-12 | 百度在线网络技术（北京）有限公司 | Method and device for carrying out abnormality test on tested program |
| CN104424090A (en) * | 2013-08-22 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Crash identifying method, device and system |
| CN104516732A (en) * | 2013-09-29 | 2015-04-15 | 北京新媒传信科技有限公司 | Application crash report method and system |
| CN104536874A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client collapse locating method and device |
| CN104657248A (en) * | 2013-11-21 | 2015-05-27 | 中国移动通信集团山东有限公司 | Java thread stack analysis method and system |
| US9122796B2 (en) | 2013-09-27 | 2015-09-01 | International Business Machines Corporation | Recreating timing issues during program debug |
| CN105068935A (en) * | 2015-09-01 | 2015-11-18 | 北京金山安全软件有限公司 | Method and device for processing software test result |
| CN105653432A (en) * | 2015-12-22 | 2016-06-08 | 北京奇虎科技有限公司 | Processing method and device of crash data |
| CN105677503A (en) * | 2016-01-13 | 2016-06-15 | 北京光年无限科技有限公司 | Software exception handling method and exception self-protection system for software |
| CN105786680A (en) * | 2016-02-17 | 2016-07-20 | 北京飞杰信息技术有限公司 | Memory preanalysis method and system adopted after kernel breakdown |
| CN105893102A (en) * | 2016-06-29 | 2016-08-24 | 北京金山安全软件有限公司 | Processing method and device for triggering blue screen by anti-virus security software and electronic equipment |
| US9442825B2 (en) | 2013-04-15 | 2016-09-13 | Tencent Technology (Shenzhen) Company Limited | Method and device for signing program crash |
| CN106133698A (en) * | 2014-03-17 | 2016-11-16 | 微软技术许可有限责任公司 | Framework for user model collapse report |
| CN106354646A (en) * | 2016-08-30 | 2017-01-25 | 竞技世界（北京）网络技术有限公司 | Method for analyzing dump files |
| CN106484617A (en) * | 2016-10-09 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | Statistical method and system are automatically analyzed for the dump file of Windows software product |
| CN106649089A (en) * | 2016-10-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Application crash analysis method and system |
| CN106708550A (en) * | 2015-11-17 | 2017-05-24 | 百度在线网络技术（北京）有限公司 | Method and device for loading shared object library |
| CN106897197A (en) * | 2015-12-17 | 2017-06-27 | 阿里巴巴集团控股有限公司 | The De-weight method and device of error log |
| CN106933689A (en) * | 2015-12-29 | 2017-07-07 | 伊姆西公司 | A kind of method and apparatus for computing device |
| CN107247667A (en) * | 2017-06-02 | 2017-10-13 | 上海金大师网络科技有限公司 | Automate dump analysis systems and method |
| CN107329896A (en) * | 2017-06-29 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of analysis method and system of the program crashing based on BE |
| US9852172B2 (en) | 2014-09-17 | 2017-12-26 | Oracle International Corporation | Facilitating handling of crashes in concurrent execution environments of server systems while processing user queries for data retrieval |
| CN107967192A (en) * | 2017-12-20 | 2018-04-27 | 北京奇虎科技有限公司 | A kind of system crash treating method and apparatus of intelligent terminal |
| CN108073507A (en) * | 2016-11-17 | 2018-05-25 | 联芯科技有限公司 | A kind of processing method and processing device of Kernel Panic field data |
| CN108153651A (en) * | 2016-12-06 | 2018-06-12 | 阿里巴巴集团控股有限公司 | The slow abnormal localization method of card, electronic equipment and system |
| CN108334515A (en) * | 2017-01-20 | 2018-07-27 | 阿里巴巴集团控股有限公司 | The method, apparatus and system of stack address in file are collapsed in a kind of processing |
| CN108459921A (en) * | 2018-02-23 | 2018-08-28 | 北京奇艺世纪科技有限公司 | Collapse file memory method, device and electronic equipment |
| CN109358975A (en) * | 2018-09-28 | 2019-02-19 | 珠海市君天电子科技有限公司 | A kind of analysis method, device, electronic equipment and storage medium that software is operating abnormally |
| CN110083471A (en) * | 2018-01-25 | 2019-08-02 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus preventing application crash |
| CN110262918A (en) * | 2019-06-19 | 2019-09-20 | 深圳市网心科技有限公司 | Process collapses analysis method and device, distributed apparatus and storage medium |
| US10489461B2 (en) | 2014-08-20 | 2019-11-26 | Oracle International Corporation | Multidimensional spatial searching for identifying substantially similar data fields |
| CN112882943A (en) * | 2021-03-11 | 2021-06-01 | 腾讯音乐娱乐科技（深圳）有限公司 | Interface updating collapse risk detection method and device, electronic equipment and storage medium |
| CN113127243A (en) * | 2019-12-30 | 2021-07-16 | 美光科技公司 | Real-time triggering of transcryption error logs |
| CN113434150A (en) * | 2021-08-30 | 2021-09-24 | 麒麟软件有限公司 | Linux kernel crash information positioning method |
| CN113467407A (en) * | 2021-09-06 | 2021-10-01 | 西安热工研究院有限公司 | Fault information collection method, system and equipment for distributed control system |
| CN116431376A (en) * | 2023-06-09 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Core dumping method, system, equipment and computer readable storage medium |
| US11971776B2 (en) | 2019-12-30 | 2024-04-30 | Micron Technology, Inc. | Real-time trigger to dump an error log |
-
2009
- 2009-12-25 CN CN200910214346A patent/CN101719090A/en active Pending
Cited By (69)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101944059A (en) * | 2010-08-20 | 2011-01-12 | 北京神州泰岳软件股份有限公司 | Automatic analysis method and device of crash information of computer software |
| CN102768639A (en) * | 2012-06-11 | 2012-11-07 | 北京奇虎科技有限公司 | Operating system kernel-level error positioning method and device |
| CN102768639B (en) * | 2012-06-11 | 2015-02-18 | 北京奇虎科技有限公司 | Operating system kernel-level error positioning method and device |
| CN103678109A (en) * | 2012-09-25 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Dump document analysis method, device and system |
| CN103678109B (en) * | 2012-09-25 | 2018-01-05 | 腾讯科技（深圳）有限公司 | A kind of dump file analysis method, device and system |
| CN102929761A (en) * | 2012-11-16 | 2013-02-13 | 赛尔网络有限公司 | System and method for responding corruption error |
| CN102929761B (en) * | 2012-11-16 | 2015-10-28 | 赛尔网络有限公司 | A kind of system and method for tackling collapsibility mistake |
| CN103106132A (en) * | 2013-03-05 | 2013-05-15 | 中标软件有限公司 | Kernel function calling stack analyzing and debugging method in case of Linux system breakdown |
| CN103106132B (en) * | 2013-03-05 | 2016-03-16 | 中标软件有限公司 | During linux system collapse, adjustment method analyzed by kernel function call stack |
| WO2014169678A1 (en) * | 2013-04-15 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Method and device for signing program crash |
| US9442825B2 (en) | 2013-04-15 | 2016-09-13 | Tencent Technology (Shenzhen) Company Limited | Method and device for signing program crash |
| CN103226510A (en) * | 2013-04-27 | 2013-07-31 | 华为技术有限公司 | Method and device for analyzing vmcore file |
| CN103226510B (en) * | 2013-04-27 | 2015-09-30 | 华为技术有限公司 | Resolve the method and apparatus of vmcore file |
| CN104142885A (en) * | 2013-05-09 | 2014-11-12 | 百度在线网络技术（北京）有限公司 | Method and device for carrying out abnormality test on tested program |
| CN104142885B (en) * | 2013-05-09 | 2019-01-11 | 百度在线网络技术（北京）有限公司 | A kind of method and apparatus for carrying out abnormality test to tested program |
| CN103309762A (en) * | 2013-06-21 | 2013-09-18 | 杭州华三通信技术有限公司 | Equipment exception handling method and device |
| CN103309762B (en) * | 2013-06-21 | 2015-12-23 | 杭州华三通信技术有限公司 | Unit exception disposal route and device |
| CN103399803A (en) * | 2013-07-29 | 2013-11-20 | 北京小米科技有限责任公司 | Method and device for collecting browser breakdown information and terminal equipment |
| CN103399803B (en) * | 2013-07-29 | 2017-05-03 | 小米科技有限责任公司 | Method and device for collecting browser breakdown information and terminal equipment |
| CN104424090A (en) * | 2013-08-22 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Crash identifying method, device and system |
| US9122796B2 (en) | 2013-09-27 | 2015-09-01 | International Business Machines Corporation | Recreating timing issues during program debug |
| CN104516732A (en) * | 2013-09-29 | 2015-04-15 | 北京新媒传信科技有限公司 | Application crash report method and system |
| CN104657248A (en) * | 2013-11-21 | 2015-05-27 | 中国移动通信集团山东有限公司 | Java thread stack analysis method and system |
| CN106133698A (en) * | 2014-03-17 | 2016-11-16 | 微软技术许可有限责任公司 | Framework for user model collapse report |
| CN106133698B (en) * | 2014-03-17 | 2020-02-07 | 微软技术许可有限责任公司 | Framework for user-mode crash reporting |
| US10489461B2 (en) | 2014-08-20 | 2019-11-26 | Oracle International Corporation | Multidimensional spatial searching for identifying substantially similar data fields |
| US9852172B2 (en) | 2014-09-17 | 2017-12-26 | Oracle International Corporation | Facilitating handling of crashes in concurrent execution environments of server systems while processing user queries for data retrieval |
| CN104536874A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client collapse locating method and device |
| CN105068935B (en) * | 2015-09-01 | 2018-09-25 | 北京金山安全软件有限公司 | Method and device for processing software test result |
| CN105068935A (en) * | 2015-09-01 | 2015-11-18 | 北京金山安全软件有限公司 | Method and device for processing software test result |
| CN106708550A (en) * | 2015-11-17 | 2017-05-24 | 百度在线网络技术（北京）有限公司 | Method and device for loading shared object library |
| CN106897197B (en) * | 2015-12-17 | 2020-07-07 | 阿里巴巴集团控股有限公司 | Error log duplicate removal method and device |
| CN106897197A (en) * | 2015-12-17 | 2017-06-27 | 阿里巴巴集团控股有限公司 | The De-weight method and device of error log |
| CN105653432A (en) * | 2015-12-22 | 2016-06-08 | 北京奇虎科技有限公司 | Processing method and device of crash data |
| CN105653432B (en) * | 2015-12-22 | 2019-02-15 | 北京奇虎科技有限公司 | A kind for the treatment of method and apparatus of crash data |
| CN106933689B (en) * | 2015-12-29 | 2020-05-19 | 伊姆西Ip控股有限责任公司 | Method and device for computing equipment |
| CN106933689A (en) * | 2015-12-29 | 2017-07-07 | 伊姆西公司 | A kind of method and apparatus for computing device |
| CN105677503A (en) * | 2016-01-13 | 2016-06-15 | 北京光年无限科技有限公司 | Software exception handling method and exception self-protection system for software |
| CN105677503B (en) * | 2016-01-13 | 2018-10-26 | 北京光年无限科技有限公司 | A kind of software anomaly processing method and the abnormal Self-Protection Subsystem for software |
| CN105786680A (en) * | 2016-02-17 | 2016-07-20 | 北京飞杰信息技术有限公司 | Memory preanalysis method and system adopted after kernel breakdown |
| CN105786680B (en) * | 2016-02-17 | 2018-06-05 | 北京飞杰信息技术有限公司 | Memory pre-analysis methods and its system after Kernel Panic |
| CN105893102B (en) * | 2016-06-29 | 2019-11-12 | 珠海豹趣科技有限公司 | A kind of processing method, device and the electronic equipment of anti-virus security software triggering blue screen |
| CN105893102A (en) * | 2016-06-29 | 2016-08-24 | 北京金山安全软件有限公司 | Processing method and device for triggering blue screen by anti-virus security software and electronic equipment |
| CN106354646A (en) * | 2016-08-30 | 2017-01-25 | 竞技世界（北京）网络技术有限公司 | Method for analyzing dump files |
| CN106354646B (en) * | 2016-08-30 | 2018-12-25 | 竞技世界（北京）网络技术有限公司 | A method of analysis dump file |
| CN106484617A (en) * | 2016-10-09 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | Statistical method and system are automatically analyzed for the dump file of Windows software product |
| CN106649089A (en) * | 2016-10-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Application crash analysis method and system |
| CN106649089B (en) * | 2016-10-09 | 2019-07-09 | 武汉斗鱼网络科技有限公司 | A kind of program crashing analysis method and system |
| CN108073507A (en) * | 2016-11-17 | 2018-05-25 | 联芯科技有限公司 | A kind of processing method and processing device of Kernel Panic field data |
| CN108153651A (en) * | 2016-12-06 | 2018-06-12 | 阿里巴巴集团控股有限公司 | The slow abnormal localization method of card, electronic equipment and system |
| CN108334515A (en) * | 2017-01-20 | 2018-07-27 | 阿里巴巴集团控股有限公司 | The method, apparatus and system of stack address in file are collapsed in a kind of processing |
| CN108334515B (en) * | 2017-01-20 | 2022-07-15 | 阿里巴巴集团控股有限公司 | Method, device and system for processing stack address in crash file |
| CN107247667A (en) * | 2017-06-02 | 2017-10-13 | 上海金大师网络科技有限公司 | Automate dump analysis systems and method |
| CN107329896A (en) * | 2017-06-29 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of analysis method and system of the program crashing based on BE |
| CN107967192A (en) * | 2017-12-20 | 2018-04-27 | 北京奇虎科技有限公司 | A kind of system crash treating method and apparatus of intelligent terminal |
| CN107967192B (en) * | 2017-12-20 | 2022-03-11 | 北京奇虎科技有限公司 | System crash processing method and device for intelligent terminal |
| CN110083471A (en) * | 2018-01-25 | 2019-08-02 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus preventing application crash |
| CN108459921A (en) * | 2018-02-23 | 2018-08-28 | 北京奇艺世纪科技有限公司 | Collapse file memory method, device and electronic equipment |
| CN109358975A (en) * | 2018-09-28 | 2019-02-19 | 珠海市君天电子科技有限公司 | A kind of analysis method, device, electronic equipment and storage medium that software is operating abnormally |
| CN110262918A (en) * | 2019-06-19 | 2019-09-20 | 深圳市网心科技有限公司 | Process collapses analysis method and device, distributed apparatus and storage medium |
| US11829232B2 (en) | 2019-12-30 | 2023-11-28 | Micron Technology, Inc. | Real-time trigger to dump an error log |
| CN113127243A (en) * | 2019-12-30 | 2021-07-16 | 美光科技公司 | Real-time triggering of transcryption error logs |
| US11971776B2 (en) | 2019-12-30 | 2024-04-30 | Micron Technology, Inc. | Real-time trigger to dump an error log |
| CN112882943A (en) * | 2021-03-11 | 2021-06-01 | 腾讯音乐娱乐科技（深圳）有限公司 | Interface updating collapse risk detection method and device, electronic equipment and storage medium |
| CN113434150A (en) * | 2021-08-30 | 2021-09-24 | 麒麟软件有限公司 | Linux kernel crash information positioning method |
| CN113467407A (en) * | 2021-09-06 | 2021-10-01 | 西安热工研究院有限公司 | Fault information collection method, system and equipment for distributed control system |
| CN113467407B (en) * | 2021-09-06 | 2021-11-16 | 西安热工研究院有限公司 | Fault information collection method, system and equipment for distributed control system |
| CN116431376B (en) * | 2023-06-09 | 2023-09-05 | 苏州浪潮智能科技有限公司 | Core dumping method, system, equipment and computer readable storage medium |
| CN116431376A (en) * | 2023-06-09 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Core dumping method, system, equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101719090A (en) | Method for automatically analyzing crash cause of computer software system | |
| CN101599039B (en) | Abnormal handling method and device under embedded type C language environment | |
| CN109240886B (en) | Exception handling method, exception handling device, computer equipment and storage medium | |
| US6182243B1 (en) | Selective data capture for software exception conditions | |
| CN101446918B (en) | Method for realizing debugging of single function by user state debugger and system thereof | |
| US20080127112A1 (en) | Software tracing | |
| US10209967B2 (en) | System and method for detecting preventative maintenance operations in computer source code | |
| CN109086193B (en) | Monitoring method, device and system | |
| JP2007500401A (en) | Software debugging apparatus and method | |
| CN102063328B (en) | System for detecting interrupt-driven type program data competition | |
| CN100388234C (en) | Method for monitoring internal memory varible rewrite based on finite-state-machine | |
| CN101667154A (en) | Apparatus and method for improving emulation speed of high-level languages in on-chip emulation systems | |
| CN1920797A (en) | Memory access control apparatus | |
| US7765434B2 (en) | Resource efficient software tracing for problem diagnosis | |
| US7793160B1 (en) | Systems and methods for tracing errors | |
| CN103049373B (en) | A kind of localization method of collapse and device | |
| CN107315961A (en) | Bug detection method and device, computing device, storage medium | |
| US8065565B2 (en) | Statistical debugging using paths and adaptive profiling | |
| US20200143061A1 (en) | Method and apparatus for tracking location of input data that causes binary vulnerability | |
| CN110647472A (en) | Breakdown information statistical method and device, computer equipment and storage medium | |
| US20180137002A1 (en) | Thread based dynamic data collection | |
| CN101533370B (en) | Memory abnormal access positioning method and device | |
| CN109885489A (en) | Data contention detection method and device in driver | |
| WO2007071615A1 (en) | Methods, apparatus and computer programs for handling parameters associated with call statements | |
| US10140476B2 (en) | Tracing processing activity |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100602 |