From: Eli Zaretskii <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: command and doco for valgrind
Date: 18 Jan 2004 16:17:11 +0200 [thread overview]
Message-ID: <ullo5nxy0.fsf@elta.co.il> (raw)
In-Reply-To: <16393.51090.62851.168340@nick.uklinux.net> (message from Nick Roberts on Sat, 17 Jan 2004 23:38:58 +0000)
> Date: Sat, 17 Jan 2004 23:38:58 +0000
> From: Nick Roberts <nickrob@gnu.org>
>
> BTW I think valgrind could be a useful tool to debug some of Emacs crashes
> (less frequent now) on x86 architectures. However, for some reason, it reports
> a memory full message at start up, at the moment:
>
> ==2466== Invalid free() / delete / delete[]
> ==2466== at 0x400263A8: free (vg_replace_malloc.c:231)
> ==2466== by 0x812A135: memory_full (alloc.c:478)
> ==2466== by 0x812A3E8: lisp_malloc (alloc.c:623)
> ==2466== by 0x812BA07: allocate_vectorlike (alloc.c:2505)
> ==2466== Address 0x83CCE60 is not stack'd, malloc'd or free'd
> emacs: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs
FWIW, this problem is documented in the valgrind's docs.
I'll try to look into this and see what I find.
next prev parent reply other threads:[~2004-01-18 14:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 21:42 command and doco for valgrind Nick Roberts
2004-01-10 12:34 ` Eli Zaretskii
2004-01-17 23:38 ` Nick Roberts
2004-01-18 7:25 ` Eli Zaretskii
2004-01-18 19:15 ` Richard Stallman
2004-01-19 6:32 ` Eli Zaretskii
2004-01-18 14:17 ` Eli Zaretskii [this message]
2004-01-18 19:15 ` Eli Zaretskii
2004-01-19 20:11 ` Richard Stallman
2004-01-19 21:33 ` Eli Zaretskii
2004-01-19 22:57 ` Nick Roberts
2004-01-20 6:21 ` EMACS and valgrind (was: command and doco for valgrind) Eli Zaretskii
2004-01-20 15:26 ` Stefan Monnier
2004-01-22 21:46 ` EMACS and valgrind Nick Roberts
2004-01-22 22:26 ` Stefan Monnier
2004-01-23 22:07 ` Nick Roberts
2004-01-24 10:25 ` Eli Zaretskii
2004-03-21 16:47 ` command and doco for valgrind Nick Roberts
2004-03-21 16:56 ` Eli Zaretskii
2004-03-22 18:27 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ullo5nxy0.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.