Package: libstdc++6
Version: 4.1.0-1+b1
Severity: normal
I came across a strange bug which I'm utterly unable to reproduce on
anything but Debian unstable (including testing on Fedora Core 5).
Basically, I've worked out (through using valgrind and gdb) that calling
ifstream::read() causes a crash
Package: g++-4.0
Version: 4.0.1-2
Severity: normal
See PR 22132, just fixed upstream. I'd very much appreciate if this fix
could be integrated to the Debian packages, especially if 4.0.2 will be
a long time in coming.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
Package: libstdc++5
Version: 1:3.3.4-6sarge1.1
Severity: serious
When upgrading from sarge to unstable, the following problem happens:
Preparing to replace libstdc++5 1:3.3.4-6sarge1.1 (using
/libstdc++5_1%3a3.3.4-9_i386.deb) ...
Unpacking replacement libstdc++5 ...
dpkg: error processing
/va
Package: g++-3.3
Version: 1:3.3.2-4
Severity: normal
The program below doesn't compile. If you change "isalnum" in ptr_fun
to "isal", it compiles just fine, though.
-- CUT HERE --
#include
#include
#include
#include
#include
using namespace std;
int isal(int c)
{
return isalnum(c)
reassign 93226 libglib1.2
rename 93266 Bit tests are redefined when G_CAN_INLINE is defined (in glib.h)
thanks
On Sat, Apr 07, 2001 at 01:56:39PM -0400, Daniel Jacobowitz wrote:
> Almost certainly not a gcc error. What and where is the definition of
> g_bit_nth_msf? It seems to be in glib-1.2/gl
Package: gcc-2.95
Version: 1:2.95.3-10
Severity: normal
When building gnome-pim, I ran into a strange problem:
gcc -shared GnomeCal-common.lo GnomeCal-stubs.lo calendar-conduit.lo calobj.lo
alarm.lo calendar.lo timeutil.lo -Wl,--whole-archive
../libversit/.libs/libversit.al -Wl,--no-whole-arch
6 matches
Mail list logo
