Adplus.exe 异常的事件日志操作不起作用
Adplus.exe EventLog action for Exceptions not working
我正在尝试调整 Adplus.exe 的配置文件,但我遇到了一个操作 EventLog
,默认情况下,它会为第二次机会异常打开。但是,我比较了有和没有 EventLog 的日志,但效果似乎是一样的。我希望它生成一个事件查看器日志,但它没有。
这是我的配置文件片段:
<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>
请注意 Exception Code='AV'
中的 EventLog
(抱歉,我无法突出显示或加粗该部分)。我试过 enabling/disabling 这个,生成的日志完全一样。 真的有效吗?如果是,在哪里可以找到事件日志?还是已经贬值了?
此外,我检查了 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
提前致谢!
找到了。它位于前缀为 !elog_str
的 DebuggerScript.txt 上。
Adding/Removing 操作中的 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 logs180312_084515_Crash_Mode
the message resource is present but the message is not found in the string/message table
Adplus 事件日志示例:
!elog_str ADPlus detected a SecondChance_av_AccessViolation in AdpProcName with Process ID AdpProcID and the output directory is AdpDumpDir;Q"
我正在尝试调整 Adplus.exe 的配置文件,但我遇到了一个操作 EventLog
,默认情况下,它会为第二次机会异常打开。但是,我比较了有和没有 EventLog 的日志,但效果似乎是一样的。我希望它生成一个事件查看器日志,但它没有。
这是我的配置文件片段:
<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>
请注意 Exception Code='AV'
中的 EventLog
(抱歉,我无法突出显示或加粗该部分)。我试过 enabling/disabling 这个,生成的日志完全一样。 真的有效吗?如果是,在哪里可以找到事件日志?还是已经贬值了?
此外,我检查了 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
提前致谢!
找到了。它位于前缀为 !elog_str
的 DebuggerScript.txt 上。
Adding/Removing 操作中的 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 logs180312_084515_Crash_Mode
the message resource is present but the message is not found in the string/message table
Adplus 事件日志示例:
!elog_str ADPlus detected a SecondChance_av_AccessViolation in AdpProcName with Process ID AdpProcID and the output directory is AdpDumpDir;Q"