quoth the Joseph Jezak:
>
> Well, that doesn't sound good. :)  Can you try using gdb to get a
> backtrace?  Maybe they're all segfaulting when using the same
> library/function call.  A backtrace from gdb would help us see that.
>
> -Joe

Thanks for the reply Joe.

Here are a few lines of context around the segfault running konsole and 
konqueror from strace, as well as links to the full output:

konsole:
http://badcomputer.org/strace_konsole.txt [427K]

 write(3, "\22\0\0\10\0\240\0\5\0\0\1H\0\0\0\4 \0\0\0\0\0\0\2\0\0"..., 1044) = 
1044
read(3, "[EMAIL PROTECTED]"..., 32) = 32
read(3, "\26\0\1A\0\240\0\27\0\240\0\27\0\240\0\n\0\0\0\0\1A\0\33"..., 32) = 
32
read(3, "\26\0\1C\0\240\0\27\0\240\0\27\0\240\0\n\0\0\0\0\1A\0\2"..., 32) = 32
read(3, "\1\3\1u\0\0\0\6\0\0\0\0\0\4K`\0\0\0\0\20\23)8\0\0\0\0\20"..., 32) = 
32
readv(3, [{"2>[EMAIL PROTECTED]|\0", 24}, {"", 0}], 2) = 
24
write(3, "e\0\0\2\10\1\0\5", 8)         = 8
read(3, "\1\6\1v\0\0\0\6\0\0\0\0\0\0\0\0\0\0\17\377\377\2526\200"..., 32) = 32
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 24) = 24
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

konqueror:
http://badcomputer.org/strace_konqueror.txt [195K]

lstat("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/usr/kde", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/usr/kde/3.5", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/usr/kde/3.5/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/usr/kde/3.5/share/apps", {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 
0
access("/usr/kde/3.5/share/apps", F_OK) = 0
lstat("/usr/kde/3.5/share/apps", {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 
0
access("/home/bulliver/.kde3.5/share/apps/konqueror/profiles/webbrowsing", 
R_OK) = 0
stat("/home/bulliver/.kde3.5/share/apps/konqueror/profiles/webbrowsing", 
{st_mode=S_IFREG|0600, st_size=642, ...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

kmail dumps this:

kbuildsycoca running...
KCrash: Application 'kmail' crashing...
DCOP aborting (delayed) call from 'anonymous-5590' to 'kmail'
ERROR: Communication problem with kmail, it probably crashed

My untrained eye cannot see anything wrong with the strace:
http://badcomputer.org/strace_kmail.txt [58K]
that is, there is no segfault.

I am going to have to read the gdb docs a bit before I can figure out how to 
use it to get a backtrace. It certainly doesn't like the fact my binaries are 
stripped. Here's what I could come up with:

  $ gdb konqueror
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc64-unknown-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/kde/3.5/bin/konqueror
(no debugging symbols found)
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
(no debugging symbols found)
kbuildsycoca running...
DCOP Cleaning up dead connections.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()

I will have a further play with gdb and post back if I learn something. I 
guess I will poke around upstream (KDE's) bugzilla and see if there is 
anything there as well.

Thanks,
-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
-- 
[EMAIL PROTECTED] mailing list

Reply via email to