Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8134167
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T09:55:15+00:00 2026-06-06T09:55:15+00:00

From the disassembly code below can I assume that the location 43E010 is a

  • 0

From the disassembly code below can I assume that the location 43E010 is a location of the variable that holds the string (as in the comment in the assembly code):

Disassembly:

...
push    offset loc_43E010
...
push    offset aAllYourBaseAre ; "all your base are belong to us"
...
.rdata:00446074 aAllYourBaseAre db 'all your base are belong to us',0

This is a disassembly code from a Win32 application that looks like this:

class Foo {
public: 
    string mystring;    
    __declspec(dllexport) void foo();
};

void Foo::foo(){

    printf("foo called");

}

int _tmain(int argc, _TCHAR* argv[])
{
    Foo foo;
    foo.mystring =  "all your base are belong to us";

    return 0;
}

Does this instruction: push offset loc_43E010 shows that address 43E010 is a offset from the base image of the win32 executable and that its a variable location?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T09:55:18+00:00Added an answer on June 6, 2026 at 9:55 am

    I’ll invoke my psychic powers (hi Raymond!) and will make a wild guess that you’re seeing something like this:

    push    ebp
    mov     ebp, esp
    push    0FFFFFFFFh
    push    offset loc_43E010
    mov     eax, large fs:0
    push    eax
    ...
    mov     large fs:0, eax
    

    This is a typical prolog of a function that uses exception handling. In your case, even though there are no try/catch statements, there is a local variable with a non-trivial destructor, which needs to be called in case there is an exception being propagated. The loc_43E010 is a label for the exception handler for the function.

    So, the answer is: no, it’s not a “variable location”.

    To learn more about exceptions in Win32 (SEH and C++), check my OpenRCE article.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am beginner at dis-assembly. Below is the disassembly of CGContextReplacePathWithShapePath from IDA pro.
I have a simple piece of assembly code that works correctly on Mac OS
I've been contemplating how to protect my C/C++ code from disassembly and reverse engineering.
I have some code, that build up a proxy from a type. It work
The code below is from the well-known article Smashing The Stack For Fun And
I'm debugging some code from the disassembly (no source code is available), and there
I'm getting the following line in the disassembly from objdump -d of an x86
how can I write just a simple disassembler for linux from scratches? Are there
From 2.13.2/3 The double quote and the question mark ? , can be represented
From time to time I run into the issue that Grails integration tests the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.