Raf wrote:
[...]
> > > the hg version still produced the error just now.
> > > i uncommented the VALGRIND definition in src/tesdir/Makefile
> > > and uncommented the LEAK_CFLAGS = -DEXITFREE line in src/Makefile
> > > and recompiled vim and reran the tests and test96 passed this time.
> > > here's the valgrind report for test96:
> > >
> > > ==8976== Memcheck, a memory error detector
> > > ==8976== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> > > ==8976== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
> > > ==8976== Command: ../vim -u unix.vim -U NONE --noplugin -s dotest.in
> > > test96.in
> > > ==8976== Parent PID: 3970
> > > ==8976==
> > > --8976-- ../vim:
> > > --8976-- dSYM directory is missing; consider using --dsymutil=yes
> > > ==8976== Warning: ignored attempt to set SIGUSR2 handler in sigaction();
> > > ==8976== the SIGUSR2 signal is used internally by Valgrind
> >
> > What compiler are you using?
>
> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> > This looks like OSX. But I thought there
> > was no valgrind for that.
>
> it's macosx-10.6.8.
> the valgrind is from macports.
> the gcc is from XCode-3.2.6.
>
> > Running with valgrind also shifts things around. Although you would be
> > really lucky if the wrong accesses happen to fall in valid memory areas.
Have you tried building without the optimizer? The gcc optimizer can be
a bit aggressive.
--
SOLDIER: Where did you get the coconuts?
ARTHUR: Through ... We found them.
SOLDIER: Found them? In Mercea. The coconut's tropical!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
