GNU bug report logs -
#9911
valgrind warning in process.c:send_process
Previous Next
Reported by: Dan Nicolaescu <dann <at> gnu.org>
Date: Sun, 30 Oct 2011 21:42:01 UTC
Severity: normal
Done: Dan Nicolaescu <dann <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sun, 06 Nov 2011 23:28:38 -0500
with message-id <yxqsjm0o8sp.fsf <at> fencepost.gnu.org>
and subject line Re: bug#9910: valgrind warning in coding.c:coding_set_destination
has caused the debbugs.gnu.org bug report #9911,
regarding valgrind warning in process.c:send_process
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
9911: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9911
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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.
[Message part 3 (message/rfc822, inline)]
Kenichi Handa <handa <at> m17n.org> writes:
> In article <yxq1utugnxb.fsf <at> fencepost.gnu.org>, Dan Nicolaescu <dann <at> gnu.org> writes:
>
>> valgrind ./temacs
>
>> produces this warning:
>
>> ==30382== Conditional jump or move depends on uninitialised value(s)
>> ==30382== at 0x499251: coding_set_destination (coding.c:1046)
>> ==30382== by 0x4B477A: decode_coding (coding.c:7022)
>> ==30382== by 0x4B7317: decode_coding_object (coding.c:7671)
>> ==30382== by 0x63610F: Fcall_process (callproc.c:813)
>> ==30382== by 0x5D6C07: Ffuncall (eval.c:2956)
>> ==30382== by 0x5D5ECA: Fapply (eval.c:2479)
>> ==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 0x622C5B: exec_byte_code (bytecode.c:785)
>> ==30382== by 0x5D77BA: funcall_lambda (eval.c:3205)
>
>> This looks like setup_coding_system (or whatever else initializes struct
>> coding_system) does not initialize the src_pos field.
>
> 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.
Thank you very much!
The fix looks good, the warning does not appear anymore.
valgrind ./temacs also segfaults for me in 32 bit mode (i686), it works
in 64 bit mode (x86_64).
This bug report was last modified 13 years and 197 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.