You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
(2) |
2
(2) |
3
|
4
|
|
5
|
6
(3) |
7
(1) |
8
(1) |
9
(4) |
10
(1) |
11
(1) |
|
12
(2) |
13
(7) |
14
(3) |
15
(2) |
16
(7) |
17
(1) |
18
(2) |
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
|
26
|
27
|
28
|
29
|
30
|
|
|
|
From: Mark W. <ma...@kl...> - 2022-06-16 22:08:27
|
Hi Martin, Let me CC valgrind-developers, maybe someone else has already looked into this. On Thu, Jun 16, 2022 at 07:19:33AM +0200, Martin Liška wrote: > Do we know what's wrong with: > https://builder.sourceware.org/buildbot/#/builders/92/builds/28 This (the opensuse tumbleweed builder) and the fedora latest builder both started failing when they upgraded to GCC 12. All other builders are green (but none use GCC 12 yet): https://builder.sourceware.org/buildbot/#/builders?tags=valgrind The failure is in make auxchecks which is not part of the normal regtests. The test builds the GNU Scientific Library gsl 1.6 and compares a testrun under valgrind. It is seeing the following failures under valgrind: +FAIL: random32-bsd, 10000 steps (852261210 observed vs 1663114331 expected) +FAIL: random64-bsd, 10000 steps (210970120 observed vs 864469165 expected) +FAIL: random32-libc5, 10000 steps (367802360 observed vs 1967452027 expected) +FAIL: random64-libc5, 10000 steps (221021662 observed vs 2106639801 expected) I haven't looked into why that is. But with earlier GCC versions these tests PASSed when run under valgrind. Cheers, Mark |
|
From: John R. <jr...@bi...> - 2022-06-16 18:04:27
|
Suggested actions: 1. File a bug report at https://bugs.kde.org against valgrind. (A bug report is the only way for valgrind developers not to forget the issue.) Give the context: the target hardware, the versions of OS and compiler and valgrind and libc and libgcc, the "32-bit only" constraint, the actual command lines you used. Be sure to include your diagnosis: >>>> The point is: >>>> - libgcc doesn't include floating point functions on powerpc, they >>>> are >>>> in libc >>>> - valgrind is built statically against libgcc, without libc 2. Possible work-around: Extract the missing functions from libc.a into separate *.o files: __floatsidf.o, __muldf3.o, __ltdf2.o, __fixdfsi.o, etc. Use something like these commands: # See if what you want really is in libc.a nm -gop libc.a | grep -E '__floatsidf|__muldf3|__ltdf2|__fixdfsi' # See the actual components of the libc.a archive ar t libc.a # Extract the files that you want ar x libc.a __floatsidf.o __muldf3.o __ltdf2.o __fixdfsi.o Then add those *.o filenames to the command line for 'ld'. |
|
From: Christophe L. <chr...@cs...> - 2022-06-16 17:16:15
|
Le 16/06/2022 à 18:54, Carl Love a écrit : > [Certaines personnes qui ont reçu ce message ne reçoivent pas souvent de courriers de ce...@us.... Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] > > On Thu, 2022-06-16 at 16:34 +0000, Christophe Leroy wrote: >> Hi Carl, >> >> Le 16/06/2022 à 18:04, Carl Love a écrit : >>> Christophe: >>> >>> On Thu, 2022-06-16 at 10:51 +0000, Christophe Leroy wrote: >>>> Hello >>>> >>>> Trying to build valgrind-3.19.0. >>>> >>>> ./configure --host=ppc-linux --prefix=/usr --enable-only32bit -- >>>> disable-tls >>>> >>>> I'm using glibc-2.35 >>>> >>>> I end up with following errors (many more of the same kind >>>> follows): >>>> >>>> /opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc- >>>> linux/bin/ld: >>>> memcheck_ppc32_linux-mc_main.o: in function `gcSecVBitTable': >>>> /home/chleroy/ldb_base/ofs/packages/valgrind- >>>> 3.19.0/memcheck/mc_main.c:993: >>>> undefined reference to `__floatsidf' >>>> >>> >>> Not sure why your using cldk-1.5.1.1rc1b1 in /opt? Not sure what >>> that >>> is? >> >> That's just the directory where sits my home built cross compiler. >> >>> When I tried the configure on a Power 10 64-bit system: >>> >>> ./configure --host=ppc-linux --prefix=/home/carll --enable- >>> only32bit >>> --disable-tls >>> >>> The configure went fine but the compile fails on >>> /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such >>> file or directory >>> >>> Not sure what system you are on and why you need the enable- >>> only32bit? >> >> I'm building on a x86_64 for running on a board which has a 32 bits >> powerpc CPU. That CPU has no FPU. >> >>> I normally build for 64-bit machines, so I tried: >>> >>> ./configure --host=ppc-linux --prefix=/home/carll --disable-tls >>> >>> I see at the end of the configure: >>> >>> Maximum build arch: ppc32 >>> Primary build arch: ppc32 >>> >>> and again get a ppc32 related build error. >>> >>> Since I am on a ppc64 LE system I did the following configure: >>> >>> ./configure --host=ppc64le-linux --prefix=/home/carll --disable- >>> tls >>> >>> Note, I am using the distro compiler /usr/bin/gcc and glibc. The >>> build >>> works fine with the distro gcc and glibc. Can you set your paths >>> to >>> use the default distro gcc and glib? >> >> I can't, I need a cross-build compiler with glibc support for my >> target. >> >> It is GCC 11 with Glibc 2.35 >> >> >>> Note, the version of glibc that I am using, as given by the ldd >>> command, is: >>> >>> $ ldd --version ldd >>> ldd (GNU libc) 2.34 >>> >> >> The point is: >> - libgcc doesn't include floating point functions on powerpc, they >> are >> in libc >> - valgrind is built statically against libgcc, without libc > > OK, I understand better the environment of what you are trying to do. > Unfortunately, I have not played in that environment so don't have a > good feel for how to fix the issue. I believe the -msoft-float option > on the compiler and linker lines will force the compiler to not > generate FP instructions but I don't think that will help in this case. > Your issue is more of a library issue. > Well, gcc is build with --with-cpu=860 and --with-float=soft so I will never generate FP instruction. Yes, the problem is a library issue and really seems linked to the fact that valgrind wants to get statically linked with libgcc only, and the following change in gcc : commit e610393ca76b204d861177a9ec542e2b4b3956cb Author: Joseph Myers <jo...@co...> Date: Thu Oct 30 17:28:30 2014 +0000 Make soft-fp symbols into compat symbols for powerpc*-*-linux*. Continuing preparations for implementing TARGET_ATOMIC_ASSIGN_EXPAND_FENV for powerpc*-*-linux* soft-float and e500, this patch makes soft-fp symbols used for those targets into compat symbols when building with glibc >= 2.19, so that they are only in shared libgcc for existing binaries requiring them, not in static libgcc and not available for new links using shared libgcc. Instead, new links will get the symbols from libc, which has exported all of them since 2.19. (Actually all the symbols were exported from glibc since 2.4, but some of them were exported by glibc as compat symbols only - because of a confusion between deliberately present soft-fp symbols and old accidental reexports of libgcc functions from glibc 2.0 - until 2.19.) I understand the reasons why valgrind wants to be linked without libc, but then what about soft-float functions ? Christophe |
|
From: Carl L. <ce...@us...> - 2022-06-16 16:54:54
|
On Thu, 2022-06-16 at 16:34 +0000, Christophe Leroy wrote:
> Hi Carl,
>
> Le 16/06/2022 à 18:04, Carl Love a écrit :
> > Christophe:
> >
> > On Thu, 2022-06-16 at 10:51 +0000, Christophe Leroy wrote:
> > > Hello
> > >
> > > Trying to build valgrind-3.19.0.
> > >
> > > ./configure --host=ppc-linux --prefix=/usr --enable-only32bit --
> > > disable-tls
> > >
> > > I'm using glibc-2.35
> > >
> > > I end up with following errors (many more of the same kind
> > > follows):
> > >
> > > /opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-
> > > linux/bin/ld:
> > > memcheck_ppc32_linux-mc_main.o: in function `gcSecVBitTable':
> > > /home/chleroy/ldb_base/ofs/packages/valgrind-
> > > 3.19.0/memcheck/mc_main.c:993:
> > > undefined reference to `__floatsidf'
> > >
> >
> > Not sure why your using cldk-1.5.1.1rc1b1 in /opt? Not sure what
> > that
> > is?
>
> That's just the directory where sits my home built cross compiler.
>
> > When I tried the configure on a Power 10 64-bit system:
> >
> > ./configure --host=ppc-linux --prefix=/home/carll --enable-
> > only32bit
> > --disable-tls
> >
> > The configure went fine but the compile fails on
> > /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such
> > file or directory
> >
> > Not sure what system you are on and why you need the enable-
> > only32bit?
>
> I'm building on a x86_64 for running on a board which has a 32 bits
> powerpc CPU. That CPU has no FPU.
>
> > I normally build for 64-bit machines, so I tried:
> >
> > ./configure --host=ppc-linux --prefix=/home/carll --disable-tls
> >
> > I see at the end of the configure:
> >
> > Maximum build arch: ppc32
> > Primary build arch: ppc32
> >
> > and again get a ppc32 related build error.
> >
> > Since I am on a ppc64 LE system I did the following configure:
> >
> > ./configure --host=ppc64le-linux --prefix=/home/carll --disable-
> > tls
> >
> > Note, I am using the distro compiler /usr/bin/gcc and glibc. The
> > build
> > works fine with the distro gcc and glibc. Can you set your paths
> > to
> > use the default distro gcc and glib?
>
> I can't, I need a cross-build compiler with glibc support for my
> target.
>
> It is GCC 11 with Glibc 2.35
>
>
> > Note, the version of glibc that I am using, as given by the ldd
> > command, is:
> >
> > $ ldd --version ldd
> > ldd (GNU libc) 2.34
> >
>
> The point is:
> - libgcc doesn't include floating point functions on powerpc, they
> are
> in libc
> - valgrind is built statically against libgcc, without libc
OK, I understand better the environment of what you are trying to do.
Unfortunately, I have not played in that environment so don't have a
good feel for how to fix the issue. I believe the -msoft-float option
on the compiler and linker lines will force the compiler to not
generate FP instructions but I don't think that will help in this case.
Your issue is more of a library issue.
Carl
|
|
From: Christophe L. <chr...@cs...> - 2022-06-16 16:50:41
|
Hi Carl, Le 16/06/2022 à 18:04, Carl Love a écrit : > Christophe: > > On Thu, 2022-06-16 at 10:51 +0000, Christophe Leroy wrote: >> Hello >> >> Trying to build valgrind-3.19.0. >> >> ./configure --host=ppc-linux --prefix=/usr --enable-only32bit -- >> disable-tls >> >> I'm using glibc-2.35 >> >> I end up with following errors (many more of the same kind follows): >> >> /opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc- >> linux/bin/ld: >> memcheck_ppc32_linux-mc_main.o: in function `gcSecVBitTable': >> /home/chleroy/ldb_base/ofs/packages/valgrind- >> 3.19.0/memcheck/mc_main.c:993: >> undefined reference to `__floatsidf' >> > > Not sure why your using cldk-1.5.1.1rc1b1 in /opt? Not sure what that > is? That's just the directory where sits my home built cross compiler. > > When I tried the configure on a Power 10 64-bit system: > > ./configure --host=ppc-linux --prefix=/home/carll --enable-only32bit > --disable-tls > > The configure went fine but the compile fails on > /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such > file or directory > > Not sure what system you are on and why you need the enable-only32bit? I'm building on a x86_64 for running on a board which has a 32 bits powerpc CPU. That CPU has no FPU. > > I normally build for 64-bit machines, so I tried: > > ./configure --host=ppc-linux --prefix=/home/carll --disable-tls > > I see at the end of the configure: > > Maximum build arch: ppc32 > Primary build arch: ppc32 > > and again get a ppc32 related build error. > > Since I am on a ppc64 LE system I did the following configure: > > ./configure --host=ppc64le-linux --prefix=/home/carll --disable-tls > > Note, I am using the distro compiler /usr/bin/gcc and glibc. The build > works fine with the distro gcc and glibc. Can you set your paths to > use the default distro gcc and glib? I can't, I need a cross-build compiler with glibc support for my target. It is GCC 11 with Glibc 2.35 > > Note, the version of glibc that I am using, as given by the ldd > command, is: > > $ ldd --version ldd > ldd (GNU libc) 2.34 > The point is: - libgcc doesn't include floating point functions on powerpc, they are in libc - valgrind is built statically against libgcc, without libc Christophe |
|
From: Carl L. <ce...@us...> - 2022-06-16 16:47:16
|
Christophe:
On Thu, 2022-06-16 at 10:51 +0000, Christophe Leroy wrote:
> Hello
>
> Trying to build valgrind-3.19.0.
>
> ./configure --host=ppc-linux --prefix=/usr --enable-only32bit --
> disable-tls
>
> I'm using glibc-2.35
>
> I end up with following errors (many more of the same kind follows):
>
> /opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-
> linux/bin/ld:
> memcheck_ppc32_linux-mc_main.o: in function `gcSecVBitTable':
> /home/chleroy/ldb_base/ofs/packages/valgrind-
> 3.19.0/memcheck/mc_main.c:993:
> undefined reference to `__floatsidf'
>
Not sure why your using cldk-1.5.1.1rc1b1 in /opt? Not sure what that
is?
When I tried the configure on a Power 10 64-bit system:
./configure --host=ppc-linux --prefix=/home/carll --enable-only32bit
--disable-tls
The configure went fine but the compile fails on
/usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such
file or directory
Not sure what system you are on and why you need the enable-only32bit?
I normally build for 64-bit machines, so I tried:
./configure --host=ppc-linux --prefix=/home/carll --disable-tls
I see at the end of the configure:
Maximum build arch: ppc32
Primary build arch: ppc32
and again get a ppc32 related build error.
Since I am on a ppc64 LE system I did the following configure:
./configure --host=ppc64le-linux --prefix=/home/carll --disable-tls
Note, I am using the distro compiler /usr/bin/gcc and glibc. The build
works fine with the distro gcc and glibc. Can you set your paths to
use the default distro gcc and glib?
Note, the version of glibc that I am using, as given by the ldd
command, is:
$ ldd --version ldd
ldd (GNU libc) 2.34
Carl Love
|
|
From: Christophe L. <chr...@cs...> - 2022-06-16 11:06:15
|
Hello
Trying to build valgrind-3.19.0.
./configure --host=ppc-linux --prefix=/usr --enable-only32bit --disable-tls
I'm using glibc-2.35
I end up with following errors (many more of the same kind follows):
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
memcheck_ppc32_linux-mc_main.o: in function `gcSecVBitTable':
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:993:
undefined reference to `__floatsidf'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:998:
undefined reference to `__floatsidf'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:998:
undefined reference to `__muldf3'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:997:
undefined reference to `__ltdf2'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:999:
undefined reference to `__muldf3'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:999:
undefined reference to `__fixdfsi'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:1008:
undefined reference to `__muldf3'
/opt/cldk-1.5.1rc1b1/lib/gcc/ppc-linux/11.2.0/../../../../ppc-linux/bin/ld:
/home/chleroy/ldb_base/ofs/packages/valgrind-3.19.0/memcheck/mc_main.c:1007:
undefined reference to `__ltdf2'
Looking at gcc history, I found:
commit e610393ca76b204d861177a9ec542e2b4b3956cb
Author: Joseph Myers <jo...@co...>
Date: Thu Oct 30 17:28:30 2014 +0000
Make soft-fp symbols into compat symbols for powerpc*-*-linux*.
Continuing preparations for implementing
TARGET_ATOMIC_ASSIGN_EXPAND_FENV for powerpc*-*-linux* soft-float and
e500, this patch makes soft-fp symbols used for those targets into
compat symbols when building with glibc >= 2.19, so that they are only
in shared libgcc for existing binaries requiring them, not in static
libgcc and not available for new links using shared libgcc. Instead,
new links will get the symbols from libc, which has exported all of
them since 2.19. ....
So I understand that libc is required to get those symbols. But I also
understand after reading comments in coregrind/m_main.c that valgrind is
intentionaly linked without libc but with libgcc only.
So how can I get the missing floating points symbols while linking
valgrind ?
Thanks
Christophe |