It looks like the flow stays inside the function TagCmp(const char*, const char*), inside a for(;;) statement. There is no exit condition for this statement and thus the application is trapped there eating up 100% CPU. Maybe the break inside the inner for-loop was supposed to break the outer one.
It looks like the flow stays inside the function TagCmp(const char*, const char*), inside a for(;;) statement. There is no exit condition for this statement and thus the application is trapped there eating up 100% CPU. Maybe the break inside the inner for-loop was supposed to break the outer one.