trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: May 2012

Re: [trinity-devel] Narrowed Time Frame 3/29->4/3 kwrite crash -> Looks like Qt3 bug

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 1 May 2012 14:34:00 -0500
> On 05/01/2012 02:12 PM, David C. Rankin wrote:
>>    I also tested kate - same crash! I don't know what Darrell is doing,
>> he
>> must be living right! I just pasted 'undefined symbol ' into line one
>> until it
>> would make it wrap and then on the next paste - wham! > crashed. This
>> backtrace is a bit different, the qt3 error I saw in kwrite appears
>> masked for
>> some reason?? Here is the kate crash backtrace:
>>
>
> This time I just opened an existing file in kate (my .bashrc). I was able
> to
> view it and resize the window, but when I started moving the cursor down
> the
> page with 'down-arrow' it locked up about 10 lines down. I don't think
> this
> backtrace adds anything, but it's short. The one thing that sticks out to
> me
> is the 'needWrap' variable. It may be nothing, but that seems to be common
> to
> the crashes:
<snip>
>    IIRC, Tim, you said the undefined symbol stuff is normal?

I don't remember saying that. :-)  The undefined symbols would explain why
your backtraces are lacking TQt3 line numbers, without which debugging is
nearly impossible.

If this really is a [T]Qt3 problem, you should be able to revert to an
earlier version and the crash should disappear.  However, I see nothing in
the log that is close to the timeframe in question, and most of the
patches for the past several months have been trivial:

http://git.trinitydesktop.org/cgit/qt3/log/

I have not yet tried to replicate this bug on any systems here.  You said
you are running this in a VirtualBox session, correct?  If so, be aware
that I have run into "TDE bugs" (crashes) before that actually turn out to
be VirtualBox bugs...

Tim