strange bug concerning kate / ksharedptr / gideon

[Daniel Engelschalt]

John Firebaugh wrote: 
 
> On Monday 10 June 2002 10:35, Daniel Engelschalt wrote: 
>> after the really strange malloc bug on friday (see 
>> http://lists.kde.org/?l=kde-devel&m=102348091719709&w=4) i completely 
>> removed kde and .kde and did a fresh compile run with todays cvs of arts
/ 
>> libs 
>> / kdevelop (gideon). but i'm still unable to start gideon and editing a 
>> file. a new 
>> backtrace can be found at the end of this mail. 
>> 
>> does anyone have an idea ? :) 
 
> Is the backtrace reproduceable? I've been getting some crashes with
bizzare 
> backtraces using kate / gideon lately. Looks like memory corruption.
Perhaps  
> someone on x86 can valgrind this? 
 
yes, the backtrace is the very same every time i start gideon. but in
valgrind it 
runs perfectly :) i'm attaching the interesting part of valgrind's output. 
 
bye, 
daniel 
 

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kate.txt.bz2
Type: application/x-bzip2
Size: 2335 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20020611/5319129b/attachment.bin>