Bug 182024 - valgrind output is very noisy.
Summary: valgrind output is very noisy.
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ncurses
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-19 09:16 UTC by Dave Jones
Modified: 2015-01-04 22:25 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-27 17:03:15 UTC


Attachments (Terms of Use)
ncurses-5.5-18.2.src.rpm (1.67 MB, application/x-rpm)
2006-02-23 15:15 UTC, Petr Raszyk
no flags Details
mutt-1.4.2.1-6.2.1.src.rpm (2.56 MB, application/x-rpm)
2006-02-23 15:17 UTC, Petr Raszyk
no flags Details
valgrind-3.1.0-1.2.src.rpm (2.94 MB, application/x-rpm)
2006-02-23 15:19 UTC, Petr Raszyk
no flags Details
valgrind-mutt.out (43.16 KB, application/octet-stream)
2006-02-24 14:43 UTC, Petr Raszyk
no flags Details

Description Dave Jones 2006-02-19 09:16:26 UTC
valgrind --error-limit=no --leak-check=yes --show-reachable=yes mutt
2>valgrind-mutt.out

valgrind-mutt.out will be filled with many instances of ..

==23073== Conditional jump or move depends on uninitialised value(s)
==23073==    at 0x392C321723: (within /usr/lib64/libncursesw.so.5.5)
==23073==    by 0x392C321C79: (within /usr/lib64/libncursesw.so.5.5)
==23073==    by 0x392C321551: _nc_scroll_optimize (in /usr/lib64/libncursesw.so.5.5)
==23073==    by 0x392C3370BF: doupdate (in /usr/lib64/libncursesw.so.5.5)
==23073==    by 0x392C32EA4B: wrefresh (in /usr/lib64/libncursesw.so.5.5)
==23073==    by 0x43A341: ??? (pager.c:1738)
==23073==    by 0x410059: ??? (commands.c:181)
==23073==    by 0x418159: ??? (curs_main.c:1070)
==23073==    by 0x42DFE0: ??? (main.c:842)
==23073==    by 0x392BA1D023: __libc_start_main (in /lib64/libc-2.3.90.so)

Comment 1 Miroslav Lichvar 2006-02-21 09:25:38 UTC
It's a problem in ncurses, there is a compiler padding in cchar_t structure and
memcmp() on the struct that wasn't memset() before causes the warning.

Comment 2 Petr Raszyk 2006-02-23 15:12:39 UTC
I do not see this as a bug in ncurses.

Please, can you compile/install *.src below
(all devel versions) and repeat your scenario:

  mutt
  valgrind
  ncurses

Many thanks.
Petr Raszyk

Comment 3 Petr Raszyk 2006-02-23 15:15:28 UTC
Created attachment 125107 [details]
ncurses-5.5-18.2.src.rpm

Comment 4 Petr Raszyk 2006-02-23 15:17:30 UTC
Created attachment 125108 [details]
mutt-1.4.2.1-6.2.1.src.rpm

Comment 5 Petr Raszyk 2006-02-23 15:19:09 UTC
Created attachment 125110 [details]
valgrind-3.1.0-1.2.src.rpm

Comment 6 Dave Jones 2006-02-24 02:30:48 UTC
These are the exact versions I already have installed, along with debuginfo's.
What would rebuilding them from source achieve ?


Comment 9 Petr Raszyk 2006-02-24 14:51:14 UTC
I do not see this as a bug in ncurses

Comment 10 Miroslav Lichvar 2006-02-27 17:03:15 UTC
It is fixed in rawhide.

Comment 11 Thomas E. Dickey 2006-03-11 19:21:40 UTC
That's interesting, but the patch does not fix the problem that
I'm interested in: ncurses supposedly initializes the cchar_t's
either via static declarations or calloc's.  I see a couple of
places where NewChar() and NewChar2() are used on the stack.
Those are probably what was reported.


Note You need to log in before you can comment on or make changes to this bug.