Message: previous - next
Month: April 2012

Re: [trinity-devel] GOOD BUILD POINT FOUND Re: [trinity-devel] kwrite/kate - why is 3.5.12 not affected (help analyzing)

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 29 Apr 2012 16:58:26 -0500
On 04/29/2012 04:27 PM, David C. Rankin wrote:
> Kwrite won't work. Kate does.

Ah, you just haven't tried hard enough yet :) Did you try the 1-2 word at a time
paste into line 1 until it wrapped in kate? That's what killed everything for me
(kwrite/kate/quanta). However as I mentioned in the other post, all work fine in
my build from 3/29.

>> I noticed the problem when I tried to launch kwrite through Konqueror to edit a text file. Kwrite started to open, a window "frame" appeared and then toast. I could not log out. I had to use Ctrl-Alt-Delete.

I have only experienced one desktop lockup that I documented in the other post.
All of the other crashes just concerned the editor at the time
(kate/kwrite/etc..) When I was using katepart preview in konqueror, that did
bring konqueror down and that was my only system lockup.

>> I started a new session. This time I started kwrite from the mini cli. No problems. Likewise from the menu. But opening through konqueror resulted in a freeze.
>> When I tried opening a file from within kwrite, the moment I started performing any cursor movements, the app froze and Ctrl-Alt-Backspace to the rescue.
>> I exited the session. I renamed the kwriterc file and removed the ksycoca cache and started a new session. Same results.
>> Interestingly, I have no problems using kate. I edited several files.

I cannot explain this. I too have had varying results with kate. I have opened
it and been able to start picking through the help documentation and had no
crash until I opened a file for editing. Once the editor part of kate is
running, if there are lines that wrap, or if I paste something that makes a line
wrap, then I can kill kate every time.

I too have had documents with long lines open in kate and had it not crash
immediately, but when I start editing, it crashes.

>> I disabled the Trinity compositing just in case. No difference.

Never even turned on in my desktop, so I can confirm this is unrelated.

>> This is a not a total session freeze. I could open konsole and konqueror. I could not logout but I did not try all methods. Possibly only the Ctrl-Alt-Delete shortcut was affected.

Yep, same here. It's just the app that crashes (unless opened from konqueror -
damn windows explorer...) That is how I was able to get the backtraces. I
usually had konsole already running, so I would just type:

  gdb --pid $(pidof kwrite)

and get gdb running, it would load the symbols, then I just typed 'bt'

I would be interested in seeing your backtrace, even without line numbers to see
if you are crashing with some of the same calls.

>> I'm unsure where we go next. We both experience kwrite issues but not kate issues. Gcc 4.7 is common but what else? NVidia? Slackware 13.1 uses xorg-server 1.7.7, Both Slackware 13.37 and Current use xorg-server 1.9.5.

gcc 4.7

xorg packages:
xorg-font-util 1.3.0-1
xorg-font-utils 7.6-3
xorg-fonts-alias 1.0.2-2
xorg-fonts-encodings 1.0.4-3
xorg-fonts-misc 1.0.1-2
xorg-mkfontdir 1.0.7-1
xorg-mkfontscale 1.1.0-1
xorg-server 1.12.1-1
xorg-server-common 1.12.1-1

video is provided by Virtualbox Video driver (I think Tim knows what this emulates)

Looking at the list of packages that I updated are Arch between the time all was
"good" and when I started getting the crashes - there was absolutely NOTHING
that looked related. No xorg changes, no font changes, no nothing, basically the
only 3rd-party packages that had changes were USB libraries and gstreamer stuff.

>> I did not perform any exhaustive testing, therefore no conclusions. This all happened in a real machine and not a virtual machine. I have not tested with Current 64-bit (I haven't yet tried to build).

I have seen the same crash in Virtualbox in both i686 and x86_64 installs. So it
has been consistent and 100% repeatable for me.

>> I use Trinity GIT in Slackware 13.1 quite a bit and never noticed anything like this. I have not noticed this with my recent Slackware 13.37 builds, but that means little because I haven't been looking for this kind of thing. That is, I don't know whether I have even used kate/kwrite in those systems because I just started building them. I will have to test more.

I didn't notice anything until my post on 4/25. I did see some "weirdness" in my
builds from 4/12 (as a matter of fact, I moved the binaries to a directory
named: 'x86_64-0412-weird') I'll go load the core packages from that build and
report back on the kwrite issue.

>> The only thing I can offer at this point is kwrite is toast in Slackware Current 32-bit.
>> Unless somebody has some clever suspicions to narrow the debugging, this could take a long while to unfold.

If we keep comparing notes and mentally eliminating things that are not related,
we can shorten this process considerably. If I was better at reading backtraces
and had a better feel for what they were telling us, then that might shorten the
search as well. Unfortunately, Tim doesn't find any smoking gun in them, so I'm
not sure how useful they are.

If you can capture a few backtraces of the crashes you see, then that at least
might point to something in common.

>> Darrell

keep the faith :)

David C. Rankin, J.D.,P.E.