Bug#385836: Fixed in NMU of plib 1.8.4-4.1

Dear Matthias Am Sun, Sep 03, 2006 at 10:32:31AM -0700 hat Matthias Klose getippert: > plib (1.8.4-4.1) unstable; urgency=low > . >* NMU. >* Drop build dependency on g++-4.0. Closes: #385836. Thanks for the NMU. Would you mind adding the patch to the BTS? Regards -- Philipp | wor

Bug#376557: ftp.debian.org: please remove callgrind/valgrind-callgrind from unstable

Package: ftp.debian.org Severity: normal The newest release of valgrind in unstable provides the functionality and the programs of the source package callgrind (was incorporated upstream). The binary package is called valgrind-callgrind. Therefore, callgrind / valgrind-callgrind needs to be remov

Bug#364796: quits immediately (Killed) when run

severity 364796 normal tags 364796 + irreproducible thanks Hi Joe Thanks for the report Am Tue, Apr 25, 2006 at 02:34:25PM -0400 hat Joe Drew getippert: > Callgrind always quits immediately on me, no matter what I do. > > [EMAIL PROTECTED]:~$ callgrind > Killed In an up-to-date unstable chroot,

Bug#334221: Problem

Makefile.am is missing from the upstream source, I have asked there for it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#334407: gbib segfaults after update

Am Mon, Oct 17, 2005 at 10:38:09PM -0700 hat Steve Langasek getippert: > If you have a valgrind report for this program, you may want > to post it to the bug report. Here it is. Please note that gbib is working under valgrind and segfaults without it on my system. Regards -- Philipp | work:

Bug#334407: gbib segfaults after update

Am Mon, Oct 17, 2005 at 10:38:09PM -0700 hat Steve Langasek getippert: > Likewise, a full backtrace may be a bit more helpful than just citing the > innermost stack frame, which only tells us "something happened somewhere > which abused the memory management interface". I get --8<--8<

Bug#334407: gbib segfaults after update

Am Mon, Oct 17, 2005 at 10:38:09PM -0700 hat Steve Langasek getippert: > Two people have tried and failed to reproduce this problem on an up-to-date > sid system. Same for me. If I set up an up-to-date chroot of sid, the problem is not reproducible. I guess upgrading the right library will fix the

Bug#334407: gbib segfaults after update

tags 33407 + confirmed help thanks Am Mon, Oct 17, 2005 at 07:35:29PM +0200 hat Peter Henseler getippert: > after upgrading from version 0.1.2-6 gbib segfaults on program startup > and dumps a core file. The command: > gdb -c core `which gbib` > tells me: > #0 0x0f77bfa0 in __gnu_cxx::__pool::_M_

Bug#329963: callgrind for valgrind 3?

Dear Josef Do you plan to release callgrind for valgrind 3? Do you already have an idea of a release date? There are already 3 Debian bugs concerning this. ;-) Thanks for a hint Sincerely -- Philipp | work: [EMAIL PROTECTED] +41 1 802 20 00 Frauenfelder | home: [EMAIL PROTECTED] +41 1 862 7

Bug#329137: Use version in testing

The version 0.9.12 of valgrind-callgrind is for valgrind up to 2.4.1. You can find valgrind 2.4 in testing. Regards -- Philipp Frauenfelder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#302711: plib: FTBFS: linker error

severity 302711 normal thanks Hi Am Sat, Apr 02, 2005 at 04:10:21PM +0200 hat Roland Stigge getippert: > building the package plib in a clean sid build environment > (with pbuilder) on i386 results in: > > = > [...] > make[2

Bug#299498: Only grave on unstable

tags 299498 + sid thanks Dear Bruce Am Tue, Mar 15, 2005 at 02:49:41PM + hat Bruce Stephens getippert: > My apologies. I hadn't noticed that this same version is used in > testing, too. Probably the package works fine with the valgrind in > testing, and is only broken in unstable. This is