- Update to 352

PR:		ports/69553
Submitted by:	Simon Barner <barner@in.tum.de> (maintainer)
This commit is contained in:
Pav Lucistnik 2004-07-25 17:02:00 +00:00
parent 06a88a1bdc
commit 210c0b78e3
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=114692
5 changed files with 7 additions and 37 deletions

View File

@ -6,7 +6,7 @@
#
PORTNAME= valgrind
PORTVERSION= 327
PORTVERSION= 352
CATEGORIES= devel
MASTER_SITES= http://www.rabson.org/
DISTNAME= ${PORTNAME}-stable-${PORTVERSION}

View File

@ -1,2 +1,2 @@
MD5 (valgrind-stable-327.tar.gz) = 56aabe03a41c4ebbb0cf2fbda3f4656a
SIZE (valgrind-stable-327.tar.gz) = 1161744
MD5 (valgrind-stable-352.tar.gz) = dcf8f9d7d9f8092d2215362c169fd0ab
SIZE (valgrind-stable-352.tar.gz) = 1228052

View File

@ -1,16 +0,0 @@
--- coregrind/vg_main.c 2004-04-10 08:32:49 UTC (rev 327)
+++ coregrind/vg_main.c 2004-04-19 09:10:49 UTC (rev 328)
@@ -1135,9 +1135,10 @@
/* Move logfile_fd into the safe range, so it doesn't conflict with any app fds */
eventually_logfile_fd = VG_(fcntl)(VG_(clo_logfile_fd), VKI_F_DUPFD, VG_(max_fd)+1);
- if (eventually_logfile_fd < 0)
+ if (eventually_logfile_fd < 0) {
+ VG_(clo_logfile_fd) = 2;
VG_(message)(Vg_UserMsg, "valgrind: failed to move logfile fd into safe range");
- else {
+ } else {
VG_(clo_logfile_fd) = eventually_logfile_fd;
VG_(fcntl)(VG_(clo_logfile_fd), VKI_F_SETFD, VKI_FD_CLOEXEC);
}

View File

@ -1,16 +0,0 @@
--- coregrind/vg_scheduler.c 2004-04-19 09:10:49 UTC (rev 328)
+++ coregrind/vg_scheduler.c 2004-04-22 08:53:06 UTC (rev 329)
@@ -1146,7 +1146,12 @@
) {
/* If __NR_exit, remember the supplied argument. */
+#ifdef __linux__
VG_(exitcode) = VG_(threads)[tid].m_ebx; /* syscall arg1 */
+#endif
+#ifdef __FreeBSD__
+ VG_(exitcode) = ((UInt*)VG_(threads)[tid].m_esp)[1]; /* syscall arg1 */
+#endif
/* Only run __libc_freeres if the skin says it's ok and
it hasn't been overridden with --run-libc-freeres=no

View File

@ -1,7 +1,9 @@
Note: This version of valgrind does not support some older AMD processors.
Note: This version of valgrind does not support some older processors,
e.g. AMD K6-III, some (?) Pentium II.
If valgrind crashes immediately after it was started with the error
message "Illegal hardware instruction", your processor is affected by
this problem.
As a workaround you can use the devel/valgrind-snapshot port, which is
based on a more recent snapshot
based on a more recent snapshot.