all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 9912@debbugs.gnu.org
Subject: bug#9912: valgrind warning in coding.c:coding_set_destination
Date: Mon, 07 Nov 2011 11:38:50 +0900	[thread overview]
Message-ID: <tl74nyglkqt.fsf@m17n.org> (raw)
In-Reply-To: <yxqy5w2f9c6.fsf@fencepost.gnu.org> (message from Dan Nicolaescu on Sun, 30 Oct 2011 17:39:05 -0400)

In article <yxqy5w2f9c6.fsf@fencepost.gnu.org>, Dan Nicolaescu <dann@gnu.org> writes:

> valgrind ./temacs 

> produces this warning:

> ==30382== Conditional jump or move depends on uninitialised value(s)
> ==30382==    at 0x636022: Fcall_process (callproc.c:799)
> ==30382==    by 0x5D6C07: Ffuncall (eval.c:2956)
> ==30382==    by 0x5D5ABB: Fapply (eval.c:2422)
> ==30382==    by 0x5D6C07: Ffuncall (eval.c:2956)
> ==30382==    by 0x622C5B: exec_byte_code (bytecode.c:785)
> ==30382==    by 0x5D77BA: funcall_lambda (eval.c:3205)
> ==30382==    by 0x5D6F4C: Ffuncall (eval.c:3023)
> ==30382==    by 0x5D5ABB: Fapply (eval.c:2422)
> ==30382==    by 0x5D6C07: Ffuncall (eval.c:2956)
> ==30382==    by 0x622C5B: exec_byte_code (bytecode.c:785)
> ==30382==    by 0x5D77BA: funcall_lambda (eval.c:3205)
> ==30382==    by 0x5D6F4C: Ffuncall (eval.c:3023)
 
> It looks like struct coding_system.dst_multibyte needs to be
> initialized.

I fixed it.  But as "valgrind ./temacs" segfaults in my
environment, I can't confirm the fix.  Please check if the
fix is correct or not.

---
Kenichi Handa
handa@m17n.org





      reply	other threads:[~2011-11-07  2:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-30 21:39 bug#9912: valgrind warning in coding.c:coding_set_destination Dan Nicolaescu
2011-11-07  2:38 ` Kenichi Handa [this message]

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=tl74nyglkqt.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=9912@debbugs.gnu.org \
    --cc=dann@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.