[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2010-12-19 Thread Launchpad Bug Tracker
[Expired for valgrind (Ubuntu) because there has been no activity for 60 days.] ** Changed in: valgrind (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2010-09-16 Thread rusivi1
Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the package version your bugging is updated in Maverick. Please update via www.ubuntu.com repost a detailed error report, and update the bug status. Thanks! -- calloc'd blocks reported as "uninitial

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2010-02-12 Thread Loïc Minier
hey there, With the latest snapshot I pushed to lucid, I exited firefox with twenty tabs or so open and ran: valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --db-attach=yes /usr/lib/firefox-3.6/firefox and it resumed all the tabs (even upgraded some extensions); when I exited aga

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2009-10-09 Thread Rebecca Palmer
It still occurs in Jaunty, but I don't have the debugging symbols for write() so haven't checked the read size fits inside the cleared block. valgrind isn't on the Karmic liveCD so I won't be testing that until release. $valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --db-attach=ye

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2009-10-08 Thread Ralph Janke
Is this symptom still reproducible in 9.04 and 9.10 beta? -- calloc'd blocks reported as "uninitialised" in X11 https://bugs.launchpad.net/bugs/134600 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bu

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2008-11-13 Thread Rebecca Palmer
Still present in Intrepid, but again I haven't checked the length of the block as gdb can't find the debugging symbols; which -dbg package is write() in? ==16593== Syscall param write(buf) points to uninitialised byte(s) ==16593==at 0x4E38E90: __write_nocancel (in /usr/lib/debug/libpthread-2.

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2008-10-18 Thread Rebecca Palmer
In Hardy, and on a different machine to the original report, the first "error" reported in Firefox under Valgrind is still a write() from a calloc'd block, but I haven't checked whether the whole of the read fits inside the calloc. I don't have Intrepid yet, but intend to get it shortly after rele

[Bug 134600] Re: calloc'd blocks reported as "uninitialised" in X11

2008-10-18 Thread Daniel T Chen
Is this symptom still reproducible in 8.10 beta or later? ** Changed in: valgrind (Ubuntu) Status: New => Incomplete -- calloc'd blocks reported as "uninitialised" in X11 https://bugs.launchpad.net/bugs/134600 You received this bug notification because you are a member of Ubuntu Bugs, whi