Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 408
  • Last Modified:

What is this assembly language doing?

Hi.

This seems to take a lot of time. Is the assembly below from the creation of Buf?
void XPControl::process_xp_buffer_event()
{
  uint32 CurrentTimeOut = 10;  // Milliseconds willing to wait for new message in GetXPMessage
  int32 retLen;   // Value Returned from GetXPMessage
  TF_TRANS *pTFTrans;
  uint8 Buf[0x4000];
 
}
lea      edi, DWORD PTR [ebp-16744]
mov      ecx, 0x105ah  
mov      eax, -0x33333334
rep stosd

Open in new window

0
nanderEire
Asked:
nanderEire
  • 7
  • 4
1 Solution
 
Infinity08Commented:
>> lea      edi, DWORD PTR [ebp-16744]
>> mov      ecx, 0x105ah  
>> mov      eax, -0x33333334
>> rep stosd

It stores the value -0x33333334 at memory location [ebp-16744]
0
 
Infinity08Commented:
>> Is the assembly below from the creation of Buf?

So, no - it does something else.
0
 
nanderEireAuthor Commented:
More specifically what does the command rep stosd do here?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Infinity08Commented:
>> what does the command rep stosd do here?

What I said : it stores the (32bit) value from register eax (-0x33333334) into the memory location specified by the register edi ([ebp-16744]).
0
 
Infinity08Commented:
Oops, I missed the "rep" part (I must not be fully awake yet lol).

Here's my revised reply :

>> what does the command rep stosd do here?

It stores the (32bit) value from register eax (-0x33333334) into the memory location specified by the register edi ([ebp-16744]), and repeats that ecx times (0x105ah = 4186) for consecutive memory locations.

Basically, it initializes a block of 16744 = 4186*4 bytes starting at address [ebp-16744] to the value -0x33333334 (repeated 4186 times)
0
 
Infinity08Commented:
Note that -0x33333334 is the same as 0xCCCCCCCC, so this might be some kind of default memory initialization of the stack.
Is this in debug mode ?
0
 
nanderEireAuthor Commented:
Yes it is in Debug. So is it likely to be the initialization of the Buf[0x4000]?
0
 
Infinity08Commented:
>> So is it likely to be the initialization of the Buf[0x4000]?

It looks like it's the initialization of that buffer, and the other local data in the function.

If you compile/run the code in release mode, it should be faster, as that initialization won't happen.

Note also, that a statically allocated buffer of size 0x4000 is quite big ... Can't you allocate it dynamically ?
0
 
nanderEireAuthor Commented:
I'm trying to optimise this program and pointed out that the buffer was huge and is being created repeatedly but they indicated that it wasn't a performance hit in release mode. Is that true?
0
 
Infinity08Commented:
>> but they indicated that it wasn't a performance hit in release mode. Is that true?

Yes. See my previous comment (http:#24023757) where I already pointed that out.

It's only in debug mode that the buffer is initialized to the pattern 0xCCCCCCCC (for reasons of detecting buffer overflows and similar errors). Due to the size of the buffer, that takes a long time.
In release mode, this kind of initialization is not done, and the allocation of the buffer is very fast (a simple increment of the stack pointer).
0
 
nanderEireAuthor Commented:
Great help. Thank you
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now