C / C++ / MFC

3-Aug-05 9:14

hi, all

I got the "First-chance exception in PrevCheck.exe: 0xC0000005: Access Violation" when the program try to access one of the library file, the application is linked to .lib file, it's accessable....

cfg.Step().Format( "Checking Day Bucket for %s", m_tmDay.Format( "%D-%b-%y" ));

if I do F11, It should go to the function of cdate.h in library
string_t CDate::Format( const char * szFormat ) const

it will go there, but the same time, Access Violation come up....
also,
"First-chance exception in Pre.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception"

could anyone tell me what to check?

Cheers,

David Crow3-Aug-05 10:18

David Crow

3-Aug-05 10:18

valerie99 wrote:
cfg.Step().Format( "Checking Day Bucket for %s", m_tmDay.Format( "%D-%b-%y" ));

could anyone tell me what to check?

The first thing I would do is break this statement down into three separate statements so that you can concentrate on one of them instead of all three.

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

valerie993-Aug-05 10:40

3-Aug-05 10:40

Thanks for your reply. I broke it down, the access violation happened when the m_tmDay.Format( "%D-%b-%y" ) calling cdate.h function

string_t CDate::Format( const char * szFormat ) const

it's definited as "CDate m_tmDay;" in header file.

Thank you!

Blake Miller3-Aug-05 10:28

Blake Miller

3-Aug-05 10:28

My suspicion is this correction required:

cfg.Step().Format( "Checking Day Bucket for %s", (LPCTSTR)(m_tmDay.Format( "%D-%b-%y" )));

valerie993-Aug-05 10:53

3-Aug-05 10:53

Thank you. I just tried it, but it still gave me the access violation.... Frown | :(

I think the problem is in cdate.h

string_t CDate::Format( const char * szFormat ) const

the "string_t" is another string library file......

don't know what to do........thanks ....

valerie993-Aug-05 12:48

Calibration in ATM machines

3-Aug-05 12:48

you saved me from hell...............!!!!!

it works!!!!!!!!!

celllllllll3-Aug-05 7:52

3-Aug-05 7:52

Hi everyone,

I have a question. Do anyone know how to detect calibration in ATM machines?
I have a autoscript .exe file. When I run the file, it opens a dialog box having CAlibration button on it. When I hit the calibration button, it does the calibration and ends without showing that when it is done.

So, what my problem is, I want to detect that calibration window and see when it closes.

Your help will be appreciated.

Thanks
Preeti

Preeti9

Maximilien3-Aug-05 8:15

Maximilien

3-Aug-05 8:15

you calibrate an automatic teller machine ?

Maximilien Lincourt
Your Head A Splode - Strong Bad

celllllllll3-Aug-05 8:23

3-Aug-05 8:23

Yes,

Please help
Thanks

Preeti

Preeti9

GKarRacer3-Aug-05 8:36

GKarRacer

3-Aug-05 8:36

Assuming it's running Windows (is it?), then you can use the standard techniques for any displayed window. For example: Use FindWindow to locate the dialog box. Periodically check if the window still exists (IsWindow). There are other methods to detect the process and when it closes provided that the process doesn't keep running after calibration is complete.

celllllllll3-Aug-05 12:16

3-Aug-05 12:16

Hi,

Yes, its running on windows. I wrote a code that opens up the window , I mean completes calibration. Same as you said, use FindWindow to locate the dialog box. Its working properly but I don't know when does it completes the calibration. I am not able to detect when that window closes.

I don't know how to use IsWindow. Can you give me more detail on that?

Also, what other methods can you use to detect a process ?

Thanks for your help.
Waiting for more details.
Thanks
Preeti

Preeti9

GKarRacer3-Aug-05 13:18

GKarRacer

3-Aug-05 13:18

IsWindow simply returns TRUE or FALSE if the specified window handle is a valid window or not. So, if it suddenly returned FALSE, obviously the window is no longer around.

Example:

HWND hWnd = FindWindow(....);
while( true )
{
   if( ! IsWindow(hWnd) )
      break;     // window is gone;
   Sleep(1000);  // wait a second for window to close
};

This is the quick and crude method. Find the window handle and periodically poll to see if the window still exists.

You can also do the same thing without polling by using a window hook. Lookup SetWindowsHook and CBTProc for more information.

To wait for the process to complete rather than the window. You need to get a process handle that's associated with that window and wait for it to close. This method, of course, will only work if the process doesn't live on after the window is destroyed.

Pseudo Example (error checking removed for brevity):

HWND   hWnd = FindWindow(...);
DWORD  ProcID;
DWORD  ThrdID = 0;
HANDLE hProcess;

ThrdID = GetWindowThreadProcessId( hWnd, &ProcID );
hProcess = OpenProcess( SYNCRONIZE, FALSE, ProcID );

// Wait for the process to complete
WaitForSingleObject( hProcess, INFINITE );
CloseHandle(hProcess);

celllllllll3-Aug-05 14:00

3-Aug-05 14:00

Thanks for your help...
I don't know but if I use here IsWindow, I am getting the same result as I was getting it earlier.

I am sending you my code ....have a look and let me know is this correct to detect the calibration , I mean when that window closes.

Here's the code:

{
CTouchScreenAPI* pTouch;
HWND hCalWin;
DWORD procId;
HANDLE hProcess;
DWORD dwWaitResult;

pTouch = CTouchScreenAPI::Create();
if (pTouch)
{
if (pTouch->Init())
pTouch->Recalibrate(FALSE);
else
MessageBox(NULL, "Created touchscreen interface OK, but Init() failed", "Info", MB_OK);

HWND hCalWin = ::FindWindow(pszABSPOINT_WND_CLASS_NAME, NULL);

while( true )
{
if( ! IsWindow(hCalWin) )
break; // window is gone;
Sleep(1000); // wait a second for window to close
};

GetWindowThreadProcessId(hCalWin, &procId);
hProcess = OpenProcess(PROCESS_ALL_ACCESS, FALSE, procId);

while (1)
{
dwWaitResult = MsgWaitForMultipleObjects(1, &hProcess, FALSE, 30*1000, QS_PAINT);
if (dwWaitResult == WAIT_OBJECT_0 + 1)
{
MSG xMsg;

while (PeekMessage(&xMsg, NULL, 0, 0, PM_REMOVE))
{
TranslateMessage(&xMsg);
DispatchMessage(&xMsg);
}
}
else if (dwWaitResult == WAIT_TIMEOUT)
{
SendMessage(hCalWin, WM_CLOSE, 0, 0);
TerminateProcess(hProcess, 0);
break;
}
else dwWaitResult == WAIT_OBJECT_0;
{
//Calibration process completed;
break;
}
}

Thanks
Preeti

Preeti9

GKarRacer4-Aug-05 6:16

GKarRacer

4-Aug-05 6:16

A couple of things:

1. Does the pTouch->Recalibrate and/or CTouchScreenAPI::Create spawn another process? Or is the recalibrate function contained within your own process (separate thread maybe?) Does recalibrate return immediately?

2. You don't necessarily need to do both the IsWindow loop and the process loop. In any case you need to call GetWindowThreadProcessId before the IsWindow loop. Otherwise, what's the point? The window is gone so the call will always fail.

3. Don't use PROCESS_ALL_ACCESS unless you absolutely have to. Use the minimum security setting to get the job done. Depending on the circumstances and user's security level the call may fail trying for all access. SYNCHRONIZE is all you need for waiting on the handle. If you need to call TerminateProcess then add PROCESS_TERMINATE as well.

4. You might want to use QS_ALLINPUT rather than QS_PAINT so that all messages get processed. See "Waiting in a message_loop"" for an example.

5. Since you're apparently doing all this in a window oriented thread (probably you're main thread), you don't want to use Sleep(1000). This will just freeze up your window while you're waiting in the loop. It'd better doing only the process wait loop, peek message loop, or using a window hook to wait for close notification of the window.

6. It's kind of pointless to call TerminateProcess immediately after SendMessage. You're not exactly giving the process much time to clean up and exit normally. Don't call TerminateProcess except as last resort.

celllllllll4-Aug-05 8:32