Package: g++-4.3
Version: 4.3.2-1.1
Severity: important
I've reduced the testcase with the Intel CESR tool to:
mutabor++ /tmp> g++ -fnon-call-exceptions -O2 cesrcut.cpp
cesrcut.cpp: In destructor SparsePreconditioner::~SparsePreconditioner():
cesrcut.cpp:282: internal compiler error: Segmentat
Forgot the attachment before...
Sorry,
Thimo
testcase.cpp
Description: Binary data
Package: g++-4.3
Version: 4.3.2-1.1
Severity: normal
*** Please type your report below this line ***
mutabor++ /tmp> g++ -fnon-call-exceptions -O2 testcase.cpp
testcase.cpp: In destructor
'SparsePreconditioner::~SparsePreconditioner()':
testcase.cpp:271: internal compiler error: Segmentation fault
Package: libgtk2.0-0
Version: 2.12.5-2
Severity: grave
Justification: renders package unusable
Starting any gtk-program ends up in a segfault inside strlen(). Here
are two example backtraces made with the debug libraries:
-- jpilot --
(gdb) r
Starting program: /usr/bin/jpilot
(no debugging symb
Hi!
I had exactly the same problem on my Alpha. After I tried a lot of
stuff I decided to change the "serial rate" to 19200. Yes, the one
which says "Does not affect USB" right next to it. But now my
USB connected Visor syncs fine with port "usb:"!
HTH
Thimo
signature.asc
Description: Digita
Hi!
As I'm encountering the same bug on my Alpha (cupsys 1.2.1-2) I'm
adding the strace-log you've asked for and which I did not see in this
bug report.
Cheers
Thimo
execve("/usr/lib/cups/backend/parallel", ["/usr/lib/cups/backend/parallel"],
[/* 29 vars */]) = 0
uname({sys="Linux", node="rif
Hi!
Are you still interested in packaging python-nltk? Your ITP is pretty
old and nothing appeared in the archive yet. There is some discussion
in this bug report but I didn't find any conclusion.
I'm asking because a non-DD asked me to sponsor his python-nltk
package. He is very python knowledga
Hi,
I don't know jack about Emacs LISP but as the bug still annoys me I've
searched for it by "interval halving". It turned out to be the
function "rng-xsd-convert-float" and in it the "positive infinity" and
"gegative infinity" which seem to raise a SIGFPE in emacs.
Just to keep you informed
Ch
Hi,
On Tue, Sep 13, 2005 at 11:44:14AM -0600, dann frazier wrote:
> Because this bug has been opened for 58 days with a patch and without a
> response, I intend to NMU ace-of-penguins in 1 week (or sooner, at the
> maintainer's request).
NMU is ok, I'm currently working on my PhD thesis :-|
Chee
Oops... forgot the attachment...
Cheers
Thimo
execve("./lamtest", ["./lamtest"], [/* 43 vars */]) = 0
uname({sys="Linux", node="riff", ...}) = 0
brk(0) = 0x120012000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.
Package: lam4-dev
Version: 7.1.1-3.2
Severity: important
I've tried the following trivial program:
#include
int
main (int argc, char **argv)
{
MPI_Init (&argc, &argv);
MPI_Finalize ();
}
Compile it:
riff /tmp> mpic++.lam lamtest.cc -o lamtest
/usr/lib/lam/include/mpi2cxx/functions_inln.h:
On Thu, Aug 25, 2005 at 02:14:04PM -0400, Clint Adams wrote:
> > That's a change in glibc? kernel? Sorry, I've missed the change,
> > perhaps you could give me a pointer?
>
> Compare /usr/include/bits/stat.h in libc6.1-dev from sarge/etch and sid.
>
> > Recompiling on my system did not fix it, th
Hi,
unfortunately the buildd machine (goedel) proved to be somewhat
2.6-immune:
http://lists.debian.org/debian-alpha/2005/08/msg00037.html
I've seen a couple of Alpha-related fixes in 2.6.13 but the rc7
doesn't even run on my home Alpha (NIC driver appears to be happy but
networking doesn't wo
On Mon, Aug 22, 2005 at 08:19:49PM -0400, Clint Adams wrote:
> > fakeroot makes my gcc behave pretty weird:
> > Maybe an 64bit issue?
>
> This may have something to do with the size and order of 'struct stat'
> changing.
That's a change in glibc? kernel? Sorry, I've missed the change,
perhaps you
Package: fakeroot
Version: 1.4.2
Severity: important
fakeroot makes my gcc behave pretty weird:
riff /tmp> cat > bla.c
int main () {}
riff /tmp> fakeroot gcc bla.c
/usr/lib/gcc/alpha-linux-gnu/4.0.2/../../../crt1.o:../sysdeps/alpha/elf/start.S:55:
undefined reference to `main'
collect2: ld retur
Package: cfengine2
Version: 2.1.14-1
Severity: normal
The changelog.Debian.gz promises:
cfengine2 (2.1.14-1) unstable; urgency=high
[...]
* Added debian/NEWS.Debian with information about extra encryption stage
added in C5 protocol which makes 2.1.14 cfagent clients unable to talk
to
Package: python2.3-twisted
Version: 1.3.0-8
Severity: important
I tried to run a twisted core and got the following error:
inferno /tmp/master> twistd --no_save -n -l - -f buildbot.tap
2005/02/21 18:01 CET [-] Log opened.
2005/02/21 18:01 CET [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.5) starti
Hi,
I've installed lcov 1.3-4 (Thanks for the --gcov-tool option!) but it
still fails with C++ code:
riff Dune/dune> lcov --directory . --gcov-tool gcov-3.4 --capture --output-file
dune.info
Capturing coverage data from .
Found gcov version: 3.4.4
Scanning . for .gcda files ...
Found 9 data file
Package: lcov
Version: 1.3-3
Severity: normal
Tags: patch
Hi,
when running lcov on a directory containing C++-sources I get the
following error:
riff Dune/dune> lcov --directory . --capture --output-file dune.info
Capturing coverage data from .
Found gcov version: 3.4.4
Scanning . for .gcda file
Package: lcov
Version: 1.3-3
Severity: wishlist
Hi,
we're developing a software which needs g++ >= 3.4 to compile
(versions below have bad bugs concerning templates). With make and
./configure passing a CXX=g++-3.4 is simple, however lcov doesn't have
a parameter to pass it a gcov-binary to use.
20 matches
Mail list logo
