GNU bug report logs -
#9948
valgrind warning: Conditional jump or move depends on uninitialised value(s) in redisplay_window
Previous Next
Reported by: Dan Nicolaescu <dann <at> gnu.org>
Date: Thu, 3 Nov 2011 21:58:01 UTC
Severity: minor
Tags: unreproducible
Done: npostavs <at> users.sourceforge.net
Bug is archived. No further changes may be made.
Full log
Message #14 received at 9948 <at> debbugs.gnu.org (full text, mbox):
> From: Dan Nicolaescu <dann <at> gnu.org>
> Cc: 9948 <at> debbugs.gnu.org
> Date: Thu, 03 Nov 2011 19:30:55 -0400
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> From: Dan Nicolaescu <dann <at> gnu.org>
> >> Date: Thu, 03 Nov 2011 17:55:03 -0400
> >>
> >> aggressive =
> >> scrolling_up
> >> ? BVAR (current_buffer, scroll_up_aggressively)
> >> : BVAR (current_buffer, scroll_down_aggressively);
> >> ^^^^^^^^^^^^^^^^^^
> >> This one
> >
> > How can this be uninitialized? This is a buffer-local value of a
> > variable that is initialized to nil on buffer.c.
>
> The line might be incorrect, are all the variables in that expression
> initialized correctly?
I think so, yes. The only other variables are:
. current_buffer -- a global variable that always has some value
. scrolling_up -- computed in the line above this snippet. It
depends on margin_pos, which is initialized at the beginning of
the parent block.
The BVAR macro doesn't reference any variables except its first
argument.
So I'm really puzzled about this one. Is there any way to ask
valgrind for a more detailed report?
This bug report was last modified 8 years and 319 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.