From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: EMACS and valgrind
Date: Fri, 23 Jan 2004 22:07:44 +0000 [thread overview]
Message-ID: <16401.39729.7130.20240@nick.uklinux.net> (raw)
In-Reply-To: <jwvfze7tyjl.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
> Now, I have no idea whether the problem you se without USE_LSB_TAG is due to
> the fact that valgrind uses a malloc implementation that returns pointers
> whose value is larger than 2^29, but it seemed like a possible cause.
It looks like USE_LSB_TAG has moved the problem from a lisp one to one of
memory allocation. As Eli has said earlier, the valgrind team have noted that
memory debugging doesn't work with Emacs:
doc> Programs which are known not to work are:
doc> * emacs starts up but immediately concludes it is out of memory and
doc> aborts. Emacs has it's own memory-management scheme, but I don't
doc> understand why this should interact so badly with Valgrind. Emacs
doc> works fine if you build it to use the standard malloc/free routines.
So I guess its not a simple problem.
Nick
next prev parent reply other threads:[~2004-01-23 22:07 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
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 [this message]
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=16401.39729.7130.20240@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--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.