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

  • Home
  • SEARCH
  • 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 6693783
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T06:01:33+00:00 2026-05-26T06:01:33+00:00

Today I’ve run across a rather strange error. Essentially what is happening is inside

  • 0

Today I’ve run across a rather strange error. Essentially what is happening is inside the function foo the first parameter is being set to the pointer value of the pointer crosssegments. So say crosssegments is location at 0x0045 then iMeaninglessdata will be set at 0x0045. If I take out iMeaninglessData and simply have o1 as the first parameter than o1 will be equal to 0x0045. If I pause the debugger before the function is called iMeaningless data and crosssegments have different pointer addresses.

void Foo(int *iMeaninglessData, handle o1, handle o2, handle o3, int iHeight, int iProfileHeight, handle o4, std::vector<object> * crossSegments, int *iProfileArray)
{
    //...code
}

Here is how I am calling the function:

std::vector<FormSummary> * crossSegmentsTop = new std::vector<FormSummary>();
int iZero = 0;
Foo(&iZero, o1, o2, o3, 10, 50, o4, crossSegmentsTop, iProfileArray);

I’m very confused as to how this could be happening. Do you think something could be happening to the stack?

Thank you,

  • Alikar
  • 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-05-26T06:01:34+00:00Added an answer on May 26, 2026 at 6:01 am

    Turns out it is a bug in the visual studio 2008 debugger when used with release mode versus debug mode. I’m generating the PDB file, but apparently until you use the value, such as in a command window, it doesn’t correctly locate the pointer for the variable.

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

Sidebar

Related Questions

today i was facing a strange problem: got a 'missing method' error on a
Today I was listening to the Hanselminutes show about .NET 3.5 SP1...What's inside ,
Today at work we came across the following code (some of you might recognize
Today I had a discussion with a colleague about nested functions in Javascript: function
Today we have received some strange exceptions on our production website. They all have
Today, reading Servlet 3.0 specification, I've come across a sentence: We emphasize that this
Today i tested my website on seo tool site and found following error: Your
Today while inside a client's production system, I found a SQL Server query that
Today's problem in my code is kind of strange, and I could not reproduce
Today I had a strange encounter with gcc. consider the following code: float len[ELEM+1];

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.