Vwwxrf

Typing CO_2 easily

How to test the sharpness of a knife?

Is there anyway, I can have two passwords for my wi-fi

Can I cause damage to electrical appliances by unplugging them when they are turned on?

Pre-Employment Background Check With Consent For Future Checks

Why does a 97 / 92 key piano exist by Bösendorfer?

Isometric embedding of a genus g surface

How to get directions in deep space?

Unable to disable Microsoft Store in domain environment

Why didn’t Eve recognize the little cockroach as a living organism?

How to preserve electronics (computers, iPads and phones) for hundreds of years

Determining multivariate least squares with constraint

Would this string work as string?

What's the name of the logical fallacy where a debater extends a statement far beyond the original statement to make it true?

Air travel with refrigerated insulin

Do I have to take mana from my deck or hand when tapping a dual land?

Cumulative Sum using Java 8 stream API

Consistent Linux device enumeration

How much do grades matter for a future academia position?

PTIJ: does fasting on Ta'anis Esther give us reward as if we celebrated 2 Purims? (similar to Yom Kippur)

Proving a complicated language is not a CFL

Has the laser at Magurele, Romania reached a tenth of the Sun's power?

Why would five hundred and five be same as one?

Do I have to know the General Relativity theory to understand the concept of inertial frame?

Error handling function (Win32/C)

Suggestions for improving error handlingError handling for function calls to parse a GIF fileWin32 GDI+ memory and styleHandling an invalid SQL query exceptionEasy error handlingErrno-like C global error handlingAutomated document downloading, with error handlingRead and write BMP file in CError-Handling Class and Logging for VBA#Error Handling- Propagating errors to calling function.

0

$begingroup$

I have written the following function to be a general "error logging" solution for my Windows API projects. Basically, given a Windows system error code (a la GetLastError()), it will log the error message into a file:

#include <Windows.h>
#include <strsafe.h>

// MAX_PATH for file name, 12 for max signed int in base 10 (-2147483648), 20 for datetime string, 5 for brackets/colon/spaces
#define MAX_DFL_LENGTH (MAX_PATH + 37)

// So that it can be used as a callback if desired
typedef VOID(CALLBACK *ERRORPROC)(DWORD, WCHAR *, INT, HANDLE, BOOL);

/**
 * Logs an error message that occurred elsewhere in the program.
 * PARAMETERS:
 * dwError - The system error code to process.
 * wszFileName - The name of the file in which the error occurred (pass __FILEW__)
 * nLine - The line at which the error was detected (pass __LINE__)
 * hOutFile - A handle to an already open file for writing the error message to.
 * fRecoverable - If true, this error is recoverable; return to the calling code. If false, exit after logging the error.
 */
VOID CALLBACK ErrorProc(
 DWORD dwError,
 WCHAR *wszFileName,
 INT nLine,
 HANDLE hOutFile,
 BOOL fRecoverable
)

 LPWSTR lpMsgBuf;
 DWORD dwWritten;
 HRESULT hr;
 UINT uLen;
 SYSTEMTIME st;
 WCHAR wszDateFileLine[MAX_DFL_LENGTH];
 CONST WCHAR *wRecovMsg[2] = L" Not recoverable, exiting program.rn", L" Recoverable; continuing execution...rn" ;

 (VOID)FormatMessageW(
 FORMAT_MESSAGE_ALLOCATE_BUFFER 

While this historically worked well enough for my personal projects, I am wondering if there are any modifications I should make to the presentation or operation of this function before suggesting its addition to a larger Windows project with an entire team of developers.

c error-handling winapi

share

asked 2 mins ago

Govind ParmarGovind Parmar

25729

$endgroup$

add a comment | 

0

$begingroup$

I have written the following function to be a general "error logging" solution for my Windows API projects. Basically, given a Windows system error code (a la GetLastError()), it will log the error message into a file:

#include <Windows.h>
#include <strsafe.h>

// MAX_PATH for file name, 12 for max signed int in base 10 (-2147483648), 20 for datetime string, 5 for brackets/colon/spaces
#define MAX_DFL_LENGTH (MAX_PATH + 37)

// So that it can be used as a callback if desired
typedef VOID(CALLBACK *ERRORPROC)(DWORD, WCHAR *, INT, HANDLE, BOOL);

/**
 * Logs an error message that occurred elsewhere in the program.
 * PARAMETERS:
 * dwError - The system error code to process.
 * wszFileName - The name of the file in which the error occurred (pass __FILEW__)
 * nLine - The line at which the error was detected (pass __LINE__)
 * hOutFile - A handle to an already open file for writing the error message to.
 * fRecoverable - If true, this error is recoverable; return to the calling code. If false, exit after logging the error.
 */
VOID CALLBACK ErrorProc(
 DWORD dwError,
 WCHAR *wszFileName,
 INT nLine,
 HANDLE hOutFile,
 BOOL fRecoverable
)

 LPWSTR lpMsgBuf;
 DWORD dwWritten;
 HRESULT hr;
 UINT uLen;
 SYSTEMTIME st;
 WCHAR wszDateFileLine[MAX_DFL_LENGTH];
 CONST WCHAR *wRecovMsg[2] = L" Not recoverable, exiting program.rn", L" Recoverable; continuing execution...rn" ;

 (VOID)FormatMessageW(
 FORMAT_MESSAGE_ALLOCATE_BUFFER 

While this historically worked well enough for my personal projects, I am wondering if there are any modifications I should make to the presentation or operation of this function before suggesting its addition to a larger Windows project with an entire team of developers.

c error-handling winapi

share

asked 2 mins ago

Govind ParmarGovind Parmar

25729

$endgroup$

add a comment | 

$begingroup$

I have written the following function to be a general "error logging" solution for my Windows API projects. Basically, given a Windows system error code (a la GetLastError()), it will log the error message into a file:

#include <Windows.h>
#include <strsafe.h>

// MAX_PATH for file name, 12 for max signed int in base 10 (-2147483648), 20 for datetime string, 5 for brackets/colon/spaces
#define MAX_DFL_LENGTH (MAX_PATH + 37)

// So that it can be used as a callback if desired
typedef VOID(CALLBACK *ERRORPROC)(DWORD, WCHAR *, INT, HANDLE, BOOL);

/**
 * Logs an error message that occurred elsewhere in the program.
 * PARAMETERS:
 * dwError - The system error code to process.
 * wszFileName - The name of the file in which the error occurred (pass __FILEW__)
 * nLine - The line at which the error was detected (pass __LINE__)
 * hOutFile - A handle to an already open file for writing the error message to.
 * fRecoverable - If true, this error is recoverable; return to the calling code. If false, exit after logging the error.
 */
VOID CALLBACK ErrorProc(
 DWORD dwError,
 WCHAR *wszFileName,
 INT nLine,
 HANDLE hOutFile,
 BOOL fRecoverable
)

 LPWSTR lpMsgBuf;
 DWORD dwWritten;
 HRESULT hr;
 UINT uLen;
 SYSTEMTIME st;
 WCHAR wszDateFileLine[MAX_DFL_LENGTH];
 CONST WCHAR *wRecovMsg[2] = L" Not recoverable, exiting program.rn", L" Recoverable; continuing execution...rn" ;

 (VOID)FormatMessageW(
 FORMAT_MESSAGE_ALLOCATE_BUFFER 

While this historically worked well enough for my personal projects, I am wondering if there are any modifications I should make to the presentation or operation of this function before suggesting its addition to a larger Windows project with an entire team of developers.

c error-handling winapi

share

asked 2 mins ago

Govind ParmarGovind Parmar

25729

$endgroup$

#include <Windows.h>
#include <strsafe.h>

// MAX_PATH for file name, 12 for max signed int in base 10 (-2147483648), 20 for datetime string, 5 for brackets/colon/spaces
#define MAX_DFL_LENGTH (MAX_PATH + 37)

// So that it can be used as a callback if desired
typedef VOID(CALLBACK *ERRORPROC)(DWORD, WCHAR *, INT, HANDLE, BOOL);

/**
 * Logs an error message that occurred elsewhere in the program.
 * PARAMETERS:
 * dwError - The system error code to process.
 * wszFileName - The name of the file in which the error occurred (pass __FILEW__)
 * nLine - The line at which the error was detected (pass __LINE__)
 * hOutFile - A handle to an already open file for writing the error message to.
 * fRecoverable - If true, this error is recoverable; return to the calling code. If false, exit after logging the error.
 */
VOID CALLBACK ErrorProc(
 DWORD dwError,
 WCHAR *wszFileName,
 INT nLine,
 HANDLE hOutFile,
 BOOL fRecoverable
)

 LPWSTR lpMsgBuf;
 DWORD dwWritten;
 HRESULT hr;
 UINT uLen;
 SYSTEMTIME st;
 WCHAR wszDateFileLine[MAX_DFL_LENGTH];
 CONST WCHAR *wRecovMsg[2] = L" Not recoverable, exiting program.rn", L" Recoverable; continuing execution...rn" ;

 (VOID)FormatMessageW(
 FORMAT_MESSAGE_ALLOCATE_BUFFER 

share

asked 2 mins ago

Govind ParmarGovind Parmar

25729

share

asked 2 mins ago

Govind ParmarGovind Parmar

25729

asked 2 mins ago

Govind ParmarGovind Parmar

25729

asked 2 mins ago

Govind ParmarGovind Parmar

25729