you used sendmessage to send a message to a window handle
the receiver of the message is not giving a response
like this:
procedure TForm1.Button1Click(Sender
begin
SendMessage(Handle, WM_USER, 0, 0);
end;
procedure TForm1.WMUser(var Msg: TMessage);
begin
repeat
Sleep(1000);
until False;
end;
you could use SendMessageTimeOut
Main Topics
Browse All Topics





by: epasquierPosted on 2009-10-21 at 02:23:49ID: 25622057
It would seem that a message does not want to be sent... Knowing which message would be the first business order
It's not going to be possible with CPU view. First, I would assume that you haven't included all the debugging information in your application, otherwise you would have at least the function name in your debug view, same way that ntdll and user32 shows the functions names (+offset of return instruction) in your call stack.
I believe you will have to kill this process and try to set a proper debug environment, where we could at least see these informations, and better yet run the code step by step when possible.
Check the project options : Linker page : Map file = Detailed (couldn't hurt), and include remote debug symbols