You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running statement "SELECT COUNT( * ) FROM MON$STATEMENTS" yields an error and an exit() call with Firebird Embedded 2.1 Beta 2. The error occurs in the following function (see Call_Stack_Failing_Place.txt):
There is a CreateFileMapping() call in the function, which fails (returns NULL) and a subsequent GetLastError() call returns 5 = ERROR_ACCESS_DENIED. What does it mean? The parameter values for the CreateFileMapping function are as follows:
This error causes Firebird to dump "MONITOR: mutex init error, status = 1" and to call the exit() function with FINI_ERROR (See Call_Stack_Before_Exit.txt).
However, running the same SELECT statement on Firebird Super Server 2.1 Beta 2 succeeds.
Submitted by: Timo Partanen (partim)
Attachments:
Call_Stack_Failing_Place.txt
Call_Stack_Before_Exit.txt
Running statement "SELECT COUNT( * ) FROM MON$STATEMENTS" yields an error and an exit() call with Firebird Embedded 2.1 Beta 2. The error occurs in the following function (see Call_Stack_Failing_Place.txt):
static bool initializeFastMutex(FAST_MUTEX* lpMutex, LPSECURITY_ATTRIBUTES lpAttributes,
BOOL bInitialState, LPCSTR lpName)
There is a CreateFileMapping() call in the function, which fails (returns NULL) and a subsequent GetLastError() call returns 5 = ERROR_ACCESS_DENIED. What does it mean? The parameter values for the CreateFileMapping function are as follows:
lpMutex->hFileMap = CreateFileMapping(
INVALID_HANDLE_VALUE,
NULL,
PAGE_READWRITE, = 4
0,
sizeof(FAST_MUTEX_SHARED_SECTION), = 16
name ); = "partim2.mon_mutex_FM_MAP"
This error causes Firebird to dump "MONITOR: mutex init error, status = 1" and to call the exit() function with FINI_ERROR (See Call_Stack_Before_Exit.txt).
However, running the same SELECT statement on Firebird Super Server 2.1 Beta 2 succeeds.
Commits: 8ffc12b
The text was updated successfully, but these errors were encountered: