(In reply to Siddhesh Poyarekar from comment #10) > It should finish a few minutes before forever :) > > The *_nocache code is O(n^3) (IIRC), so it's very very slow.
Hi. Thanks for your quick reply. With that kind of complexity I'll adopt your heuristic: if no failure in 5 minutes, assume success. > If you want to do a correctness test then I'd suggest commenting out the > get_next_seq_cached paths so that get_next_seq_nocache is called all the > time and then run your usual strcoll correctness tests. Thanks for the suggestion, I'll force get_next_seq_nocache and run my strcoll faithfulness tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048203 Title: (CVE-2012-4412) glibc: strcoll() integer overflow leading to buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1048203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
