|
From: Dirk M. <mu...@kd...> - 2005-07-19 19:20:02
|
SVN commit 436438 by mueller: backport -r4108 from valgrind-3.0 M +1 -10 configure.in =20 --- trunk/valgrind/configure.in #436437:436438 @@ -290,16 +290,7 @@ AC_CACHE_CHECK([for PIE support], vg_cv_pie, [AC_ARG_ENABLE(pie, [ --enable-pie platform supports= PIE linking], [vg_cv_pie=3D$enableval], - [safe_CFLAGS=3D$CFLAGS - CFLAGS=3D"$CFLAGS -fpie" - safe_LDFLAGS=3D$LDFLAGS - LDFLAGS=3D"$LDFLAGS -pie" - AC_TRY_LINK([int foo;], - [], - [vg_cv_pie=3Dyes], - [vg_cv_pie=3Dno]) - CFLAGS=3D$safe_CFLAGS - LDFLAGS=3D$safe_LDFLAGS])]) + [vg_cv_pie=3Dno] )]) if test "$vg_cv_pie" =3D yes; then AC_DEFINE([HAVE_PIE], 1, [can create position-independent executables]) fi |
|
From: Dirk M. <mu...@kd...> - 2005-07-27 12:35:28
|
SVN commit 439205 by mueller: - backport inotify syscalls to 2.4 - add NEWS - bump version M +40 -0 NEWS =20 M +1 -1 configure.in =20 M +8 -0 coregrind/linux/core_os.h =20 M +79 -0 coregrind/linux/syscalls.c =20 M +1 -1 coregrind/vg_syscalls.c =20 M +14 -3 coregrind/x86-linux/syscalls.c =20 M +11 -11 coregrind/x86-linux/vki_unistd.h =20 |
|
From: Dirk M. <mu...@kd...> - 2005-07-27 12:52:24
|
SVN commit 439218 by mueller: sync README with 3.0 M +19 -18 README =20 --- trunk/valgrind/README #439217:439218 @@ -14,15 +14,15 @@ =20 Executive Summary ~~~~~~~~~~~~~~~~~ -Valgrind is a GPL'd system for debugging and profiling x86-Linux program= s. -With the tools that come with Valgrind, you can automatically detect -many memory management and threading bugs, avoiding hours of frustrating -bug-hunting, making your programs more stable. You can also perform -detailed profiling to help speed up your programs. +Valgrind is an award-winning suite of tools for debugging and profiling +Linux programs. With the tools that come with Valgrind, you can +automatically detect many memory management and threading bugs, avoiding +hours of frustrating bug-hunting, making your programs more stable. You = can +also perform detailed profiling, to speed up and reduce memory use of yo= ur +programs. =20 -The Valgrind distribution includes five tools: two memory error +The Valgrind distribution currently includes five tools: two memory erro= r detectors, a thread error detector, a cache profiler and a heap profiler= . -Several other tools have been built with Valgrind. =20 To give you an idea of what Valgrind tools do, when a program is run under the supervision of the first memory error detector tool, all reads @@ -63,31 +63,32 @@ =20 Building and installing it ~~~~~~~~~~~~~~~~~~~~~~~~~~ -To install from CVS : +To install from the Subversion repository : =20 - 0. Check out the code from CVS, following the instructions at - http://developer.kde.org/source/anoncvs.html. The 'modulename' is - "valgrind". + 0. Check out the code from SVN, following the instructions at + http://valgrind.org/devel/cvs_svn.html. =20 1. cd into the source directory. =20 2. Run ./autogen.sh to setup the environment (you need the standard autoconf tools to do so). =20 + 3. Continue with the following instructions... + To install from a tar.bz2 distribution: =20 - 3. Run ./configure, with some options if you wish. The standard + 4. Run ./configure, with some options if you wish. The standard options are documented in the INSTALL file. The only interesting one is the usual --prefix=3D/where/you/want/it/installed. =20 - 4. Do "make". + 5. Do "make". =20 - 5. Do "make install", possibly as root if the destination permissions + 6. Do "make install", possibly as root if the destination permissions require that. =20 - 6. See if it works. Try "valgrind --tool=3Dmemcheck ls -l". Either - this works, or it bombs out with some complaint. In that case, - please let us know (see www.valgrind.org). + 7. See if it works. Try "valgrind ls -l". Either this works, or it + bombs out with some complaint. In that case, please let us know + (see www.valgrind.org). =20 Important! Do not move the valgrind installation into a place different from that specified by --prefix at build time. This will @@ -96,5 +97,5 @@ =20 =20 Julian Seward (js...@ac...) -Nick Nethercote (nj...@ca...) +Nick Nethercote (nj...@va...) Jeremy Fitzhardinge (je...@go...) |
|
From: Dirk M. <mu...@kd...> - 2005-07-27 16:43:42
|
SVN commit 439276 by mueller:
- compile against glibc 2.4
- compile against gcc 4.0.x
M +1 -0 NEWS =20
M +2 -2 README =20
M +65 -1 configure.in =20
A glibc-2.4.supp glibc-2.3.supp#439275
M +1 -1 memcheck/tests/scalar.c =20
M +1 -1 none/tests/x86/Makefile.am =20
--- trunk/valgrind/NEWS #439275:439276
@@ -27,6 +27,7 @@
- fix stabs debug info reading for FreePascal binaries
- update syscall table to include new syscalls included in
Linux 2.6.13.
+- updates to compile properly with gcc 4.x and glibc 2.4
=20
New features:
=20
--- trunk/valgrind/README #439275:439276
@@ -47,8 +47,8 @@
=20
Valgrind is closely tied to details of the CPU, operating system and
to a less extent, compiler and basic C libraries. This makes it
-difficult to make it portable, so I have chosen at the outset to
-concentrate on what I believe to be a widely used platform: x86/Linux.
+difficult to make it portable. Nonetheless, it is available for
+the following platforms: x86/Linux, AMD64/Linux and PPC32/Linux.
=20
Valgrind is licensed under the GNU General Public License, version 2.=20
Read the file COPYING in the source distribution for details.
--- trunk/valgrind/configure.in #439275:439276
@@ -193,6 +193,16 @@
],
glibc=3D"2.3")
=20
+AC_EGREP_CPP([GLIBC_24], [
+#include <features.h>
+#ifdef __GNU_LIBRARY__
+ #if (__GLIBC__ =3D=3D 2 && __GLIBC_MINOR__ =3D=3D 4)
+ GLIBC_24
+ #endif
+#endif
+],
+glibc=3D"2.4")
+
AC_MSG_CHECKING([the glibc version])
=20
case "${glibc}" in
@@ -214,9 +224,15 @@
DEFAULT_SUPP=3D"${DEFAULT_SUPP} glibc-2.3.supp"
;;
=20
+ 2.4)
+ AC_MSG_RESULT(2.4 family)
+ AC_DEFINE([GLIBC_2_4], 1, [Define to 1 if you're using glibc 2.4.x])
+ DEFAULT_SUPP=3D"${DEFAULT_SUPP} glibc-2.4.supp"
+ ;;
+
*)
AC_MSG_RESULT(unsupported version)
- AC_MSG_ERROR([Valgrind requires the glibc version 2.1, 2.2 or 2.3])
+ AC_MSG_ERROR([Valgrind requires the glibc version 2.1, 2.2, 2.3 or 2.4]=
)
;;
esac
=20
@@ -269,6 +285,54 @@
])
CFLAGS=3D$safe_CFLAGS
=20
+USE_MMX_REGISTER=3D""
+AC_MSG_CHECKING([if gcc accepts -mmmx ])
+
+safe_CFLAGS=3D$CFLAGS
+CFLAGS=3D"-mmmx"
+
+AC_TRY_COMPILE(, [
+int main () { return 0 ; }
+],
+[
+handles_mmmx=3Dyes
+AC_MSG_RESULT([yes])
+], [
+handles_mmmx=3Dno
+AC_MSG_RESULT([no])
+])
+
+if test "$handles_mmmx" =3D "yes"; then
+ USE_MMX_REGISTER=3D"-mmmx"
+fi
+
+AC_SUBST([USE_MMX_REGISTER])
+
+USE_SSE_REGISTER=3D""
+AC_MSG_CHECKING([if gcc accepts -msse ])
+
+safe_CFLAGS=3D$CFLAGS
+CFLAGS=3D"-msse"
+
+AC_TRY_COMPILE(, [
+int main () { return 0 ; }
+],
+[
+handles_msse=3Dyes
+AC_MSG_RESULT([yes])
+], [
+handles_msse=3Dno
+AC_MSG_RESULT([no])
+])
+
+if test "$handles_msse" =3D "yes"; then
+ USE_SSE_REGISTER=3D"-msse"
+fi
+
+AC_SUBST([USE_SSE_REGISTER])
+
+
+
if test x$no_pointer_sign =3D xyes; then
CFLAGS=3D"$CFLAGS -Wno-pointer-sign"
fi
--- trunk/valgrind/memcheck/tests/scalar.c #439275:439276
@@ -14,7 +14,7 @@
// PRE_MEM_READ/PRE_MEM_WRITE calls. (Note that Memcheck and Addrcheck =
will
// always issue an error message immediately before these seg faults occ=
ur).
=20
-#include <asm/ipc.h>
+//#include <asm/ipc.h>
#include <sched.h>
#include <signal.h>
=20
--- trunk/valgrind/none/tests/x86/Makefile.am #439275:439276
@@ -24,7 +24,7 @@
$(INSN_TESTS) \
int pushpopseg rcl_assert seg_override
=20
-AM_CFLAGS =3D $(WERROR) -Winline -Wall -Wshadow -g -I$(top_srcdir)/inc=
lude
+AM_CFLAGS =3D $(WERROR) -Winline -Wall -Wshadow -g -I$(top_srcdir)/inc=
lude $(USE_MMX_REGISTER) $(USE_SSE_REGISTER)
AM_CXXFLAGS =3D $(AM_CFLAGS)
=20
# generic C ones
|
|
From: Nicholas N. <nj...@cs...> - 2005-07-27 16:47:08
|
On Wed, 27 Jul 2005, Dirk Mueller wrote: > --- trunk/valgrind/README #439275:439276 > @@ -47,8 +47,8 @@ > > Valgrind is closely tied to details of the CPU, operating system and > to a less extent, compiler and basic C libraries. This makes it > -difficult to make it portable, so I have chosen at the outset to > -concentrate on what I believe to be a widely used platform: x86/Linux. > +difficult to make it portable. Nonetheless, it is available for > +the following platforms: x86/Linux, AMD64/Linux and PPC32/Linux. Is it a bad idea to say this in the 2.4.0 branch? N |
|
From: Dirk M. <mu...@kd...> - 2005-07-27 16:57:56
|
On Wednesday 27 July 2005 18:46, Nicholas Nethercote wrote: > Is it a bad idea to say this in the 2.4.0 branch? damn, too many checkous. -- Dirk//\ |
|
From: Dirk M. <mu...@kd...> - 2005-07-27 16:58:06
|
SVN commit 439304 by mueller: revert last commit M +2 -2 README =20 --- trunk/valgrind/README #439303:439304 @@ -47,8 +47,8 @@ =20 Valgrind is closely tied to details of the CPU, operating system and to a less extent, compiler and basic C libraries. This makes it -difficult to make it portable. Nonetheless, it is available for -the following platforms: x86/Linux, AMD64/Linux and PPC32/Linux. +difficult to make it portable, so I have chosen at the outset to +concentrate on what I believe to be a widely used platform: x86/Linux. =20 Valgrind is licensed under the GNU General Public License, version 2.=20 Read the file COPYING in the source distribution for details. |
|
From: Dirk M. <mu...@kd...> - 2005-07-28 22:27:07
|
SVN commit 439786 by mueller:
bump version number here too.
M +1 -1 coregrind/docs/coregrind_intro.html =20
M +1 -1 docs/manual.html =20
--- trunk/valgrind/coregrind/docs/coregrind_intro.html #439785:439786
@@ -101,7 +101,7 @@
Helgrind has been hacked on extensively by Jeremy
Fitzhardinge, and we have him to thank for getting it to a
releasable state.
- <p><em>Note:</em>Helgrind is not functioning in 2.4.0; we hope to
+ <p><em>Note:</em>Helgrind is not functioning in 2.4.x; we hope to
resurrect it for the next release.
<p>
</ul>
--- trunk/valgrind/docs/manual.html #439785:439786
@@ -25,7 +25,7 @@
<body bgcolor=3D"#ffffff">
=20
<a name=3D"title"> </a>
-<h1 align=3Dcenter>Valgrind, version 2.4.0</h1>
+<h1 align=3Dcenter>Valgrind, version 2.4.1</h1>
<center>This manual was last updated on 4 March 2005</center>
<p>
=20
|