Bug#576334: marked as done (std::bad_alloc thrown in regression tests [armel powerpc s390])

2010-04-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Apr 2010 19:42:35 -0400 with message-id and subject line Version: 2.2-13 has caused the Debian Bug report #575002, regarding std::bad_alloc thrown in regression tests [armel powerpc s390] to be marked as done. This means that you claim that the problem has been dealt wi

Bug#576334:

2010-04-03 Thread Christopher L Conway
Michael Tautschnig reports: The problem, at least for most of the build failures, is a very simple one: An endianness issue, which actually lies in the original MiniSat code. The declaration of d_assigns in line 251 of src/sat/minisat_solver.h declares the assignments as a vector of chars; assign

Bug#576334: Cloning for std::bad_alloc on armel powerpc s390

2010-04-03 Thread Christopher L Conway
This version of the bug is for tracking the failures on armel, powerpc, and s390. (armel doesn't print the std::bad_alloc message, but it fails in the same place. Let's assume this is the same bug for now.) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "u