|
Debug Error!
File i386\chkesp.c
Line 42
The value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention.
|
|
|
|
|
In Debug mode, the stack is verified after every function call to make sure that every thing is playing nicely in your program.
The message states why the problem usually happens, however it can happen when you corrupt the stack because of writing to a bad address with invalid pointers and other things.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
Ok, I see, but I don't know why this is happening in my program...It crashes after this function call but the strange thing is this. This function add strings to a linked list. First it checks the linked list to make sure that the string isn't already there, if it doesn't find it then it adds it. The program crashes only when it finds a match in the linked list and the string is more than 37 chars in length. Anything under that is OK. That is what is confusing me. Maybe you can have a look at this code?
void movie_list::AddTo_Gimme(char szMovieName[][51], int iNumber)
{
movie_list_element *pSearch;
char szBuffer[80];
int x;
for (x = 0; x < iNumber; x++)
{
pSearch = first_movie;
// Search for a match
while (pSearch != NULL)
{
if ( strcmp(szMovieName[x], pSearch->movie_name) == 0 )
break;
else
pSearch = pSearch->next_movie;
}
if (pSearch == NULL)
{
// No match; Add the movie to the head of the list
movie_list_element *NewMovie;
NewMovie = new movie_list_element;
NewMovie->movie_name = strdup(szMovieName[x]);
NewMovie->next_movie = first_movie;
first_movie = NewMovie;
}
}
}
Thanks for the help so far.
|
|
|
|
|
Ahhhh, the stupidity of a bottle of wine and five in the morning!!!!!!!!!!! The buffer to hold the formatted string was too small. Now I can rest in peace...sorry to bother with this stupidity!
|
|
|
|
|
georgiek50 wrote:
The buffer to hold the formatted string was too small. Now I can rest in peace...
Good for you, I am glad you found it!
georgiek50 wrote:
sorry to bother with this stupidity!
No problem, often these kind of questions make me and other people think about things that we would have otherwise not seen. It is also a way for you to bounce ideas off the wall and think about them even if you solve the problem your self.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
Does anyone have a C++ implementation for the PSOLA Algorithm?
|
|
|
|
|
Hi All
Does anybody know of or seen a amazing set of functions that can be used to anchor and resize an object to its dialog form, so when teh dialog in resized/maximised, the objects resize and position themselves.
(I hope so otherwise i'm gonna have to role my sleeves up)
Cheers
Matt G
|
|
|
|
|
I believe MSDN mag published such a framework a little while ago.
One REALLY cool thing about .NET is the way all of this is so easy now.
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
I've got a library to do this that I was going to put up as an article when I had a bit of spare time (HA!). How much of a hurry are you in?
|
|
|
|
|
Sorry for the delay. Not an amazing hurry but i would be grateful if you could let me know when you have put it in as an article.
Thanks
Matt
Matt G
|
|
|
|
|
|
Thanks, it looks pretty good.
Matt G
|
|
|
|
|
There are a bunch of articles here on CP. Check out the dialog section.
Software Zen: delete this;
|
|
|
|
|
I have an MDI application where I am able to print text into multiple pages , but when I perform Zoom Zoom out or next page I do not get the desired page number.
How do I manage the pages that i generated ?
|
|
|
|
|
This sounds like a bug in your OnPrint() function. In this function you need to check the value of pInfo->m_nCurPage to see which out you need to draw/plot. In preview mode, the pages may be requested in any order, so your code needs to be able to plot any specific page separately. You probably have some code that saves state and then prints the next page on etc.
Roger Allen
Sonork 100.10016
I have a terminal disease. Its called life!
|
|
|
|
|
Previously I had always installed them into Windows\System32 but with VC7 the merge modules for MFC and CRT by default install the DLL's into the application directory.
Have Microsoft changed the policy on this? do all DLL's go into app directory now?
|
|
|
|
|
Yes, in theory Microsoft want to keep System32 uncluttered. This keeps with the whole 'have everything you need to run the app in the one directory' approach that will be a boon to software pirates in coming years.
There is, of course, no reason not to put them in System32 if you want to.
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
|
I like it, too. I have a big hard drive, I don't care. I'm just pointing out that it will aid piracy.
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
|
|
|
|
|
Do it like the pro's and save yourself a lot of grief: link statically.
|
|
|
|
|
For many years now, I've always copied the DLL's into the application directory. I got so fed up with some other application overwriting the system DLL's with older versions and breaking my app.
However, where possible I avoid linking to the MFC DLL's and use static linking instead. Helps a lot when distributing applications over the internet and also makes updating users systems easier.
Michael
Life’s not a song.
Life isn’t bliss.
Life is just this.
It’s living. -- Buffy the Vampire Slayer: Once more, with feeling
|
|
|
|
|
I am having a brain freeze (happens with no sleep . . .) Anyway, I have a third party ActiveX control (single OCX file with several controls in it) and I want to get the IID, CLSID, and LIBID for one of the controls. Can anyone refresh my memory on how to do this?
In desparate need of sleep . . .
Zac
"If I create everything new, why would I want to delete anything?"
|
|
|
|
|
If you have the typelib (or if it is embedded in the .ocx) you can view it using OLE/COM Object viewer - View TypeLib from there. All these GUIDs should be in there.
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
|
|
|
|
|
I'm completely new to programming, so this question will probably provide some laughs for you experienced people. What is the difference between the Heap and the Stack? And is this difference addressed by any code techniques? In other words, is this important, or does Windows manage memory without having to make the distinction? Another question; When you guys refer to a memory leak, is this exclusively 'heap leak' or 'stack leak', or does it even matter? And, are these locations assignable?
|
|
|
|
|
Well... I guess you've already written some programs in C or C++, right? If so, unless you have used malloc or new, all the variables declared and used in your program live on the stack. They're automatically added and removed on a stack-like manner as the flow of execution progress. For instance:
int a=0;
int b=10;
for(a=0;<b;++a){
int i=2*a;
}
Get the idea? The lifespan of stack variables is automatically taken care of by the compiler.
Sometimes, however, you need to have a variable that lives longer that the context it is declared in. These can be seen as "floating" variables whose birth and death is under control of the programmer, not the compiler --you decide when the variable is created, and when it is destroyed. The space these variables live in is called the heap. In C/C++, heap variables are handled though pointers:
int * a;
...
void f()
{
a=new int;
}
...
delete a; This is a very shallow introduction to the concepts, any basic C++ tutorial will explain these things better and in more detail.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
