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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937088 Title: Gosmore hangs on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosmore/+bug/937088/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
