all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: nickrob@gnu.org, emacs-devel@gnu.org
Subject: Re: command and doco for valgrind
Date: Sun, 18 Jan 2004 14:15:13 -0500	[thread overview]
Message-ID: <E1AiIO9-00060O-AB@fencepost.gnu.org> (raw)
In-Reply-To: <uvfn9k9a9.fsf@elta.co.il> (message from Eli Zaretskii on 18 Jan 2004 09:25:50 +0200)

I'm not too surprised that unexec runs into trouble with valgrind.
unexec is not a 100% implementation of undumping; it handles only the
cases that people needed to make it handle.  If valgrind moves outside
that envelope, problems occur.

It may be possible to debug the problem by running temacs with args -l
loadup.  That way you can do the debugging without ever dumping Emacs.

  reply	other threads:[~2004-01-18 19:15 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 [this message]
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
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=E1AiIO9-00060O-AB@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@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.