public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/28457] New: ext/pb_ds/regression/tree_data_map_rand.cc fails with a particular random seed. Date: Sat, 22 Jul 2006 01:55:00 -0000 [thread overview] Message-ID: <bug-28457-3264@http.gcc.gnu.org/bugzilla/> (raw) I saw a failure in this test while testing another patch. I reran the test a number of times and couldn't reproduce it, but fortunately it prints out its random seed. I hacked that value into the initial seed in util/regression/rand/assoc/rand_regression_test.hpp, and now it fails 100% of the time: detected leaks! 0x59c570: 515, 0 Failure at /space/fsf/commit/gcc/libstdc++-v3/testsuite/util/regression/rand/assoc/detail/operator_fn_imps.hpp: 192 container: Test failed with seed 1153519516 -- Summary: ext/pb_ds/regression/tree_data_map_rand.cc fails with a particular random seed. Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: drow at gcc dot gnu dot org GCC host triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28457
next reply other threads:[~2006-07-22 1:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-22 1:55 drow at gcc dot gnu dot org [this message] 2006-07-26 11:26 ` [Bug libstdc++/28457] " pcarlini at suse dot de 2006-07-26 13:11 ` drow at gcc dot gnu dot org 2006-07-26 13:27 ` pcarlini at suse dot de 2006-07-26 14:55 ` pcarlini at suse dot de 2006-08-25 17:19 ` pcarlini at suse dot de 2006-10-06 10:41 ` bkoz at gcc dot gnu dot org 2006-10-06 16:07 ` pcarlini at suse dot de 2009-07-15 7:38 ` steven at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-28457-3264@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).