c++ - How does one pass on parameters in assembly? -

-

im working on the hook in C ++ and ASM and at present I have just made an easy inline hook which is already Jumps in the direction of the target function which in this case the output debug string is for testing purposes only.

This thing is that my hook fiancé works after about three days of research and how some things work, its bits and peaks are detected, but

As you can see in my code I have tried, there is a problem. I do not know how to change the parameters that come in my "dummy" function. To change the parameter in C ++, but of course it does not work as a pop in all registers later: /

Anyway this is my dummy function which is how to hook hook functions Jumps from:

Fixed zero __declspec (naked) MyDebugString (LPCTSTR lpOutputString) {__asm ​​{PUSHAD} // Where I think I can run my code, but do not take anymore To interfere with the parameter: / lpOutputString = L "New Message!"; __asm ​​{POPAD MOV EDI, EID Push EBP MOV EBP, ESP JMP Adrer} Original debugstring (LP overputstring); }

I understand why the code is not working as I said, I can not see the proper solution, no help is greatly appreciated.

Each compiler has a protocol to call functions using assembly language. The protocol can be said in depth in its manual.

Function is a fast way to find the protocol that the compiler prepares an assembly language list for your function.

The best way to write an inline assembly is to:

  1. Type the function in the first C ++ source code
  2. The assembly list function of the next print.
  3. Review and understand how the compiler-generated assembly works.
  4. In the end, modify the internal assembly according to your needs.

My priority can be written as C ++ as efficient as code (or compiler to help in optimal assembly language) I then review the assembly list Do I change the inline assembly only to start the processor's special features (like block-driving instructions).


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more