On Tue, 2006-02-14 at 19:45 +0100, Mathias Krause wrote:
> The preprocessor from gcc 4.0.x behaves wrong when using the "-iquote"
> option as recommended by a warning when using "-I-".
The documentation states:
In addition, `-I-' inhibits the use of the directory of the current
file dir
Margarita,
I am not a Debian developer, but do have some advice about your leak
report.
I am only familiar with valgrind, not leaktracer or ccmalloc. However,
reading the valgrind results, the report indicates reachable memory, not
a leak:
>==19195== LEAK SUMMARY:
>==19195==definitely lost:
On Thu, 2004-02-05 at 04:25, Daniel Kraft wrote:
> ... having a way to make libstdc++ free [its memory pool]
> would make finding real leaks easier.
See the valgrind FAQ, question #14:
http://valgrind.kde.org/faq.html
Quoting...
Using gcc, you can force the STL to use malloc and to free
Gunther,
[I'm not a DD; just a helping hand...]
On Thu, 2004-01-15 at 08:33, Gunther Laure wrote:
> Example code:
> ...
> catch(...)
> {
> std::cout << "catched "<< &number << std::endl;
> }
> ...
I am unable to reproduce your problem using my vanilla sid install:
g++-3.3 [3.3.3-0pre2]
Package: g++-3.0
Version: 1:3.0.4-7
Severity: wishlist
Tags: patch
There is a small typo (an extra period) in the README.Debian
file of gcc-3.0. The patch is inline below.
--- README.Debian.orig 2003-01-28 21:18:13.0 -0500
+++ README.Debian 2003-01-28 21:18:21.0 -0500
@@ -
5 matches
Mail list logo