delphi - Infinity loop on Message Queue -

-

i'm working injected dll inside process. in dll create 1 thread among other things set 2 timers , keyboardhook (setwindowshookex wh_keyboard_ll)... make hook , 2 timers work, needed create 1 message pump procedure. , call message pump last thing on thread, can see in thread.execute:

procedure mymainthread.execute; begin   while not terminated     begin       mythread:= self;       startkeyboardhook;       startup;       settimer(0, 0, 60000, @mymainthread.contacthome);       settimer(0, 0, 40000, @mymainthread.mapproc);          createmessagepump;       terminate;     end; end;

ok, after createmessagepump call, terminate, because believe message pump 1 infinity loop, , if out that, wrong occurs need terminate thread. createmessagepump on this:

procedure mymainthread.createmessagepump; var   appmsg: tmsg; begin   while getmessage(appmsg, 0, 0, 0)     begin       translatemessage(appmsg);       dispatchmessage(appmsg);     end;   //if needed quit procedure use postquitmessage(0); end;

i'm doing correct way? mean, correct believe loop infinite?

the loop in execute method pointless. since final act of loop body call terminate loop body can run once. write this:

procedure mymainthread.execute; begin   mythread:= self;   startkeyboardhook;   startup;   settimer(0, 0, 60000, @mymainthread.contacthome);   settimer(0, 0, 40000, @mymainthread.mapproc);      createmessagepump; end;

your message loop fine. people may warn check return value of getmessage more closely, usage fine. see raymond's discussion of topic: http://blogs.msdn.com/b/oldnewthing/archive/2013/03/22/10404367.aspx

it's not clear, seems plausible passing timer procedure not compatible required function signature. declaration of settimer in windows unit results in no type checking being performed on callback pass. means can pass absolutely anything. fact compiler compels use @ operator warning sign have problem.

the way out stop using @ operator, , use fixed declaration of settimer. should use code sertac provided in 1 of earlier questions: using process32first/next inside dll procedure.


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

c++ - Clear the memory after returning a vector in a function -

-
i have function processes , stores lot of data in , returns results vector of class. amount of data stored in function tremendous , want clear storage memory of function after finished job. necessary (does function automatically clear memory) or should clear memory function? update: vector<customers> process(char* const *filename, vector<int> id) { vector<customers> list_of_customers; (perform actions) return list_of_customers; } variables defined locally within function automatically released @ end of function scope. destructors objects called, should free memory allocated objects (if objects coded correctly). example of such object std::vector . anything you've allocated new must have corresponding delete release storage. try avoid doing own allocation , use raii instead, i.e. containers or smart pointers.
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more