Syserr Renewal (RE)

[Owsap 14266]

This is the hidden content, please

• Sign In
• or
• Sign Up

Alternative download links →

This is the hidden content, please

• Sign In
• or
• Sign Up

 About

• Logs are now timestamped and moved to a dedicated `/syserr` folder
• Files older than 30 days are purged on run-time
• Client now gathers `syserr` and `dxdiag` logs into `syserr/crash/` during a crash

Looking for CrashRpt Support?

• CrashRpt v.1.4.3 r1645
• Full support with Syserr Renewal
• Preconfigured with automatic crash dump generation and stack trace support.
   

This is the hidden content, please

• Sign In
• or
• Sign Up

 

Alternative download links → 

This is the hidden content, please

• Sign In
• or
• Sign Up

 

This is the hidden content, please

• Sign In
• or
• Sign Up

[Owsap 14266]

Integrating CrashRpt into the Syserr Renewal is a practical improvement!

Quote

CrashRpt is a free open-source library designed for intercepting exceptions in your C++ program, collecting technical information about the crash and sending error reports over the Internet to software vendor.

When used with Syserr Renewal, crash logging becomes significantly more useful for debugging.
The generated report can include:

• Stack trace
• Function names
• Module names
• Source file names
• Line numbers

This requires compiling with debug symbols enabled. These details can also be hidden through configuration options if needed.

For security reasons, encrypting the generated dump and report files is a good idea, especially if they are transmitted over the network.

Below is a simple crash simulation example:

PyObject* appExit(PyObject* poSelf, PyObject* poArgs)
{
	// TEST_CRASH
	assert("bug");
	*((char*)NULL) = 0;
	// END_TEST_CRASH

	CPythonApplication::Instance().Exit();
	return Py_BuildNone();
}

This forces an access violation and allows you to verify that CrashRpt correctly captures and reports the crash.
The goal is to provide clearer, more actionable crash reports for faster analysis and debugging.

Edited February 20 by Owsap

[bossy_max 1]

is there an arrangement for vs13?

[flatik 232]

On 10/18/2022 at 8:04 PM, bossy_max said:

is there an arrangement for vs13?

why are you using the old version?
2022 in visual studio is 64bit, it won't freeze up all the time.

[DemOnJR 1213]

For MartySama source:

Change:
TCHAR* szModule = ""; 
To:
const TCHAR* szModule = "";

Change:
CreateProcess("C:\\Windows\\System32\\dxdiag.exe", "/dontskip /whql:off /t dxdiag_log.txt", NULL, NULL, FALSE, CREATE_NO_WINDOW, NULL, crash_path.c_str(), &si, &pi)
To:
CreateProcessA("C:\\Windows\\System32\\dxdiag.exe", const_cast<LPSTR>("/dontskip /whql:off /t dxdiag_log.txt"), NULL, NULL, FALSE, CREATE_NO_WINDOW, NULL, crash_path.c_str(), &si, &pi)

Also keep in mind the minidump

#if !defined(_EXTENDED_ERROR_LOG_)
#define ENABLE_CRASH_MINIDUMP
#endif

Edited July 18, 2023 by DemOnJR

[Owsap 14266]

This topic has been updated with the reverse engineered code of the syserr handling.

CrashRpt support remains included and improved.

[martysama0134 10731]

About CrashRpt:

• By default, the CrashSender.exe will require the c++ runtime libraries to be installed. It can be recompiled with CRASHRPT_LINK_CRT_AS_DLL=OFF to compile it as /MT.
• This line can be used to include a screenshot of the player's client during the crash.

  	crAddScreenshot2(CR_AS_MAIN_WINDOW | CR_AS_USE_JPEG_FORMAT, 95);