Exception的Adplus.exe EventLog操作无效

时间:2018-03-12 10:48:38

标签: adplus

我正在尝试调整Adplus.exe的配置文件,但我遇到了一个操作EventLog,默认情况下会为第二次机会异常启用。但是,我比较了有和没有EventLog的日志,但似乎效果是一样的。我希望它生成一个事件查看器日志,但它没有。

这是我的cfg片段:

<Exception Code='eh'>
  <Actions1> Log;stack;</Actions1>
  <ReturnAction1> GN </ReturnAction1>
</Exception>
<Exception Code='AV'>
  <Actions1> Log;stack;FullDump;EventLog</Actions1>
  <ReturnAction1> GN </ReturnAction1>
</Exception>
<Exception Code='*'>
  <Actions1> Log;stack </Actions1>
  <ReturnAction1> GN </ReturnAction1>
</Exception>
<Exception Code='epr'>
  <Actions1> Log;</Actions1>
</Exception>
<Exception Code='bpe'>
  <Actions1> Log </Actions1>
  <ReturnAction1> GN </ReturnAction1>
</Exception>

请注意EventLog中的Exception Code='AV'(抱歉,我无法突出显示或加粗该部分)。我尝试启用/禁用此功能,生成的日志完全相同。 真的有效吗?如果是,可以在哪里找到事件日志?或者它已经折旧了?

另外,我检查了Adplus v7文档,EventLog不包括在内,但就像我说的那样, 更新:它不在文档中但是在我们运行ADPlus –HelpConfig时显示。

默认情况下,它启用了第二次机会异常,如下面生成的DebuggerScript.txt

所示
*| Default Exception Behavior:
*|     Action1: Log
*|     Return1: GN
*|     Action2: Log;Time;Stack;FullDump;EventLog
*|     Return2: Q
*| Default Event Behavior:
*|     Action1: Log
*|     Return1: GN
*| 
*| Exceptions:
*| av-AccessViolation
*|     Action1: Log;stack;FullDump
*|     Return1: GN
*|     Action2: Log;Time;Stack;FullDump;EventLog
*|     Return2: Q
*| ch-InvalidHandle
*|     Action1: Log
*|     Return1: GN
*|     Action2: Log;Time;Stack;FullDump;EventLog
*|     Return2: Q

预先谢谢!

1 个答案:

答案 0 :(得分:0)

找到它。它位于DebuggerScript.txt上,前缀为!elog_str

在操作中添加/删除EventLog并未更改日志中的任何内容,因为默认情况下它始终为“第二次机会例外”启用。此外,事件日志仅显示实际事件查看器日志的描述。

实际事件查看器日志示例:

The description for Event ID 0 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

ADPlus detected a SecondChance_clr_NET_CLR in ExceptionGenerator.exe with Process ID 5516 and the output directory is logs\20180312_084515_Crash_Mode

the message resource is present but the message is not found in the string/message table

Adplus EventLog示例:

!elog_str ADPlus detected a SecondChance_av_AccessViolation in AdpProcName with Process ID AdpProcID and the output directory is AdpDumpDir;Q"
相关问题