Which the initial values of the iterator exception error when the interrupt-CodePudding

if (! Running) return;
glClear(GL_COLOR_BUFFER_BIT);
Char id [3].
/* the draw the your cursors */
STD: : listSTD: : listIter=cursorList. The begin ();
For (; Iter!=cursorList. End (); Iter++) {
Iter TuioCursor * tcur=(*);
STD: : list Path=tcur - & gt; GetPath ();
If (path. The size () & gt; 0)
{
TuioPoint last_point=path. The front ();
GlBegin (GL_LINES);
GlColor3f (0.0, 0.0, 1.0);
For (STD: : list : : iterator point=path. The begin (); Point!=path. The end (); Point++)
{
GlVertex3f (last_point getScreenX (width), last_point. GetScreenY (height), 0.0 f);
GlVertex3f (point - & gt; GetScreenX (width), point - & gt; GetScreenY (height), 0.0 f);
Last_point. Update (point - & gt; GetX (), point - & gt; GetY ());
}
GlEnd ();

/* the draw the finger tip # */
GlColor3f (0.75, 0.75, 0.75);
STD: : listIf (be!=jointCursorList. End ())
{
GlColor3f (0.5, 0.5, 0.5);
}
GlPushMatrix ();
GlTranslatef (last_point getScreenX (width), last_point. GetScreenY (height), 0.0 f);
GlBegin (GL_TRIANGLE_FAN);
For (double a=0.0 f; A. & lt;=2 * M_PI; A +=0.2 f)
{
GlVertex2d (cos * height/100.0 f (a), sin (a) * height/100.0 f);
}
GlEnd ();
GlPopMatrix ();
GlColor3f (0.0, 0.0, 0.0);
GlRasterPos2f (tcur - & gt; GetScreenX (width), tcur - & gt; GetScreenY (height));
Sprintf (id, "% d", tcur - & gt; GetCursorID ());
DrawString (id);
}
}

This is part of the source code, debug debugging when I go to the iter=cursorList. The begin (); Directly interrupt abnormal, Release under normal operation, mystery, bosses, rounding

CodePudding user response:

Interrupt a hint what hair

CodePudding user response:

This is me after the call stack to list the inside of the container code

CodePudding user response:

STD: : list & amp; cursorList=tuioServer - & gt; GetTuioCursors ();
So try

CodePudding user response:

After this is tried

CodePudding user response:

I saw your stack with thread start inside function
Threads are you?
Check your tuioServer and member function returns the object lifetime
Threads run half you these objects are the destructor

CodePudding user response:

Right, it is multithreaded, ok, I check

CodePudding user response:

Bosses, I in the destructor tuioServer add debugging information, but in the interrupt occurs, the debugging information does not appear, you don't have a destructor