16,471
社区成员
发帖
与我相关
我的任务
分享First-chance exception in ussdAgent.exe (RPCRT4.DLL): 0xC0000005: Access Violation!
它并不影响的运行.但肯定是某个地方发生异常了!
这究竟是什么异常呢? 有人说是指针违例.
可我看我的程序相关地方.并没有发现指针违例呀!
这究竟是什么异常呢? 有人说是指针违例.
可我看我的程序相关地方.并没有发现指针违例呀!
...全文
请发表友善的回复…
发表回复
jiajie828 2004-08-26
- 打赏
- 举报
谢谢大家！
jiajie828 2004-08-26
- 打赏
- 举报
以前相同帖子别人的回答
The first-chance exception can be ignored because it is safely handled by the operating system.
INFO: First and Second Chance Exception Handling (Q105675)
Structured exception handling (SEH) takes a little getting used to, particularly when debugging. It is common practice to use SEH as a signaling mechanism. Some application programming interfaces (APIs) register an exception handler in anticipation of a failure condition that is expected to occur in a lower layer. When the exception occurs, the handler may correct or ignore the condition rather than allowing a failure to propagate up through intervening layers. This is very handy in complex environments such as networks where partial failures are expected and it is not desirable to fail an entire operation simply because one of several optional parts failed. In this case, the exception can be handled so that the application is not aware that an exception has occurred.
However, if the application is being debugged, it is important to realize that the debugger will see all exceptions before the program does. This is the distinction between the first and second chance exception. The debugger gets the "first chance," hence the name. If the debugger continues the exception unhandled, the program will see the exception as usual. If the program does not handle the exception, the debugger will see it again (the "second chance"). In this latter case, the program normally would have crashed had the debugger not been present.
If you do not want to see the first chance exception in the debugger, then disable the feature. Otherwise, during execution, when the debugger gets the first chance, continue the exception unhandled and allow the program to handle the exception as usual. Check the documentation for the debugger that you are using for descriptions of the commands to be used.
The first-chance exception can be ignored because it is safely handled by the operating system.
INFO: First and Second Chance Exception Handling (Q105675)
Structured exception handling (SEH) takes a little getting used to, particularly when debugging. It is common practice to use SEH as a signaling mechanism. Some application programming interfaces (APIs) register an exception handler in anticipation of a failure condition that is expected to occur in a lower layer. When the exception occurs, the handler may correct or ignore the condition rather than allowing a failure to propagate up through intervening layers. This is very handy in complex environments such as networks where partial failures are expected and it is not desirable to fail an entire operation simply because one of several optional parts failed. In this case, the exception can be handled so that the application is not aware that an exception has occurred.
However, if the application is being debugged, it is important to realize that the debugger will see all exceptions before the program does. This is the distinction between the first and second chance exception. The debugger gets the "first chance," hence the name. If the debugger continues the exception unhandled, the program will see the exception as usual. If the program does not handle the exception, the debugger will see it again (the "second chance"). In this latter case, the program normally would have crashed had the debugger not been present.
If you do not want to see the first chance exception in the debugger, then disable the feature. Otherwise, during execution, when the debugger gets the first chance, continue the exception unhandled and allow the program to handle the exception as usual. Check the documentation for the debugger that you are using for descriptions of the commands to be used.
oyljerry 2004-08-25
- 打赏
- 举报
程序肯定有问题的
Kudeet 2004-08-25
- 打赏
- 举报
看看这个帖子对你有没有帮助
http://community.csdn.net/Expert/topic/2971/2971645.xml?temp=.7803003
http://community.csdn.net/Expert/topic/2971/2971645.xml?temp=.7803003
holyeagle 2004-08-25
- 打赏
- 举报
Exception Handling Functions for Debugging
When an exception occurs in a process that is being debugged, the system notifies the debugger by passing the exception to it. This is known as first-chance notification. The system then suspends all threads in the process being debugged.
If the debugger does not handle the exception, the system attempts to locate an appropriate exception handler. If the system cannot locate an appropriate one, the system again notifies the debugger that an exception has occurred. This is known as last-chance notification. If the debugger does not handle the exception after the last-chance notification, the system terminates the process being debugged.
For more information, see Debugger Exception Handling.
调试的时候发生异常，系统的的一种处理方式。可能无害，但一定和程序有关，有可能是断点点，断言，调试信息，都可以产生异常，从而触发系统处理。可以参考一下MSDN。
When an exception occurs in a process that is being debugged, the system notifies the debugger by passing the exception to it. This is known as first-chance notification. The system then suspends all threads in the process being debugged.
If the debugger does not handle the exception, the system attempts to locate an appropriate exception handler. If the system cannot locate an appropriate one, the system again notifies the debugger that an exception has occurred. This is known as last-chance notification. If the debugger does not handle the exception after the last-chance notification, the system terminates the process being debugged.
For more information, see Debugger Exception Handling.
调试的时候发生异常，系统的的一种处理方式。可能无害，但一定和程序有关，有可能是断点点，断言，调试信息，都可以产生异常，从而触发系统处理。可以参考一下MSDN。
jiajie828 2004-08-25
- 打赏
- 举报
程序并不出错.只是Debug时输出这样的调试信息!
DentistryDoctor 2004-08-25
- 打赏
- 举报
应该是访问违则，再仔细检查栎的程序，再看看出问题时的调用堆栈吧。
