From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: jdonner Newsgroups: gmane.emacs.devel Subject: Re: valgrind Date: Tue, 12 Aug 2003 21:28:59 -0600 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <3F39B07B.9030102@earthlink.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1060745499 13392 80.91.224.253 (13 Aug 2003 03:31:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 13 Aug 2003 03:31:39 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Aug 13 05:31:37 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19mmML-0006NW-00 for ; Wed, 13 Aug 2003 05:31:37 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19mmUL-0003Gm-00 for ; Wed, 13 Aug 2003 05:39:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19mmKH-0001fu-NR for emacs-devel@quimby.gnus.org; Tue, 12 Aug 2003 23:29:29 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19mmJG-0001R2-6S for emacs-devel@gnu.org; Tue, 12 Aug 2003 23:28:26 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19mmIj-0008Bd-VL for emacs-devel@gnu.org; Tue, 12 Aug 2003 23:28:24 -0400 Original-Received: from [207.217.120.12] (helo=harrier.mail.pas.earthlink.net) by monty-python.gnu.org with esmtp (Exim 4.20) id 19mmIQ-00078p-5I for emacs-devel@gnu.org; Tue, 12 Aug 2003 23:27:34 -0400 Original-Received: from sdn-ap-003caburbp0186.dialsprint.net ([63.184.16.186] helo=earthlink.net) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19mmIO-0006up-00 for emacs-devel@gnu.org; Tue, 12 Aug 2003 20:27:32 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030721 X-Accept-Language: en-us, en Original-To: emacs-devel@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:15918 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:15918 Robert Anderson wrote: > Has anyone ever looked into why emacs doesn't play well > with valgrind? It dies immediately with: > .. Joe Buehler > My guess would be undump() -- the build process creates > the final emacs binary by starting emacs, loading up some > LISP files, then writing all its memory out to a > new executable. I get the same crash when using valgrind on a recent CVS build; is Joe Buehler's explanation correct? Is anyone using valgrind or purify on emacs? Here are the errors again, for reference: ... ==10911== Invalid free() / delete / delete[] ==10911== at 0x40029CF7: realloc (in /usr/lib/valgrind/vgskin_memcheck.so) ==10911== by 0x8162E97: xrealloc (alloc.c:547) ==10911== by 0x815B13B: regex_compile (regex.c:2716) ==10911== by 0x816204B: re_compile_pattern (regex.c:5994) ==10911== Address 0x8457848 is not stack'd, malloc'd or free'd ==10911== ==10911== Invalid free() / delete / delete[] ==10911== at 0x400299D9: free (in /usr/lib/valgrind/vgskin_memcheck.so) ==10911== by 0x8162D86: memory_full (alloc.c:478) ==10911== by 0x8162ED8: xrealloc (alloc.c:552) ==10911== by 0x815B13B: regex_compile (regex.c:2716) ==10911== Address 0x82FDBE0 is not stack'd, malloc'd or free'd emacs: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs ==10911== ... Jeff Donner