Subject: bug#9911: valgrind warning in process.c:send_process

From: Kenichi Handa <[email-masked]>
Date: Mon, 07 Nov 2011 11:39:06 +0900

In article <[email-masked]>, Dan Nicolaescu <[email-masked]> writes:

> valgrind ./temacs 

> produces this warning

> ==30382== Conditional jump or move depends on uninitialised value(s)
> ==30382==    at 0x6302A9: send_process (process.c:5398)
> ==30382==    by 0x630DC8: Fprocess_send_string (process.c:5648)
> ==30382==    by 0x5D6D61: Ffuncall (eval.c:2977)
> ==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 0x622C5B: exec_byte_code (bytecode.c:785)
> ==30382==    by 0x5D77BA: funcall_lambda (eval.c:3205)
> ==30382==    by 0x5D6F4C: Ffuncall (eval.c:3023)
> ==30382==    by 0x622C5B: exec_byte_code (bytecode.c:785)
> ==30382==    by 0x5D77BA: funcall_lambda (eval.c:3205)
> ==30382==    by 0x5D6F4C: Ffuncall (eval.c:3023)

> Looks like struct coding_system.src_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
[email-masked]