Back to General and Gameplay Programming

problems remove()ing with std::list

Ezbez · 2006-07-09T05:42:28

To start off, I will describe what I am doing a bit. It may seem a bit irrelevant at the moment, but it might clarify things a bit later. I am using MSVC++ 2005 EE to create a GUI system. I have a Window class which is a standard widget/window/whatever you want to call it. A Window can have child Windows (and, hence, a parent Window). I use an std::list to keep track of which Windows are children of a Window, and a pointer to the parent Window of the Window. Now, when a Window is given input focus, it has the parent Window remove it from the list of child Windows and then add it again. My problem is with the removing of the Window from the child Windows list. I use this function: void Window::RemoveChild(Window *removedChild) { //childWindows is the std::list childWindows.remove(removedChild); } However, my program crashes on this line, inside of the remove() call. I get an error message of "list incrementor not incrementable" on line 236 of the list header. Now, this makes me think that removedChild isn't actually inside of remove(). But, I've looked through my code and I can't see how it could not be in there. See, the only way that a child Window can get focus is from a parent Window giving it focus. The only way that RemoveChild() is callled is form a child Window (*parentWindow is checked to be != NULL and I set parentWindow to NULL in the constructor), and it is passed this, so it's not getting the wrong pointer. I've also tried std::find() then erase()ing the found iterator, and writing my own finding algorithm. All of these get the same error that a list iterator cannot be incremented. Well, any suggestions? I don't really know what other code I could possibly show you, since it all _seems_ to be in order. Thanks in advanced.

General and Gameplay Programming Programming

Started by Ezbez July 05, 2006 08:06 PM

12 comments, last by GameDev.net 17 years, 9 months ago

joanusdmentia

1,060

July 07, 2006 08:25 AM

Quote:Original post by Ezbez
I'm sorry, but I don't quite understand what you mean. Which lines in particular would be the "offending" ones? The declarations of my Windows? Adding the child Windows to the parent Windows? I will test out using new on my Windows, though.

Sorry, by the offending lines I mean those which directly cause the error (eg. comment out the call to RemoveChild).

Quote:Original post by Ezbez
And I'm sorta sure that my problem with debugging comes from using SDL. Would I need to use a special debugging library instead of the typical SDL library?

Edit: some of my debugger output is:

"'OpenGLApplication.exe': Loaded 'C:\Documents and Settings\Owner\Desktop\Tom's Useless Junk\OpenGL Games\Gravitas\Debug\SDL.dll', Binary was not built with debug information."

I doubt that's the problem, most (all?) of the standard Windows DLLs you use would be built without debug information. All that means is that you can't step into the code of those DLLs and have any idea where you are, you'll only get the actual CPU instructions being executed in the disassembly view.

"Voilà! In view, a humble vaudevillian veteran, cast vicariously as both victim and villain by the vicissitudes of Fate. This visage, no mere veneer of vanity, is a vestige of the vox populi, now vacant, vanished. However, this valorous visitation of a bygone vexation stands vivified, and has vowed to vanquish these venal and virulent vermin vanguarding vice and vouchsafing the violently vicious and voracious violation of volition. The only verdict is vengeance; a vendetta held as a votive, not in vain, for the value and veracity of such shall one day vindicate the vigilant and the virtuous. Verily, this vichyssoise of verbiage veers most verbose, so let me simply add that it's my very good honor to meet you and you may call me V.".....V

Ezbez

1,164

Author

July 08, 2006 05:29 AM

Quote:Original post by joanusdmentia
Sorry, by the offending lines I mean those which directly cause the error (eg. comment out the call to RemoveChild).

Well, I comment out that, and the program runs fine. Just the child Windows don't re-order based on focus.

Ezbez

1,164

Author

July 09, 2006 04:14 AM

Alright, I have a fairly major update.

I compiled my project with Code::Blocks using GCC to compile. And, surprisingly, it worked perfectly. There's no crash and does what it's supposed to do, too.

This first led me to think that there was possibly a bug in Microsoft's implementation of the standard library. But, I found that unlikely seeing as this is their 8th version of it.

So, do you think it is Microsoft's error, or do I have a devious error that will probably hide for a while under GCC and then resurface again?

[Edited by - Ezbez on July 9, 2006 4:14:36 AM]

Anonymous

July 09, 2006 05:42 AM

Quote:Original post by Ezbez
Alright, I have a fairly major update.

I compiled my project with Code::Blocks using GCC to compile. And, surprisingly, it worked perfectly. There's no crash and does what it's supposed to do, too.

This first led me to think that there was possibly a bug in Microsoft's implementation of the standard library. But, I found that unlikely seeing as this is their 8th version of it.

So, do you think it is Microsoft's error, or do I have a devious error that will probably hide for a while under GCC and then resurface again?

Yes, you have a hidden bug somewhere that corrupts your data. Problems like that are hard to find.

problems remove()ing with std::list

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

problems remove()ing with std::list

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines