Can you please provide:
a) an better backtrace, as described http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports
b) the document that makes konqueror crash

Thanks.

Pino:

Thanks for replying.
Have worked through your reference site and installed the necessary programs 
to produce a more useful back trace.  Down load was very slow.
Okay got the file kdelibs-dbg, and kdepim-dbg.

first try:
Crashed konqueror with mouseover a "xenos PDFout" file, and here is the 
backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232824112 (LWP 6944)]
[KCrash handler]
#6  0xb7d45610 in rawmemchr () from /lib/tls/i686/cmov/libc.so.6
#7  0xb7d3a396 in ?? () from /lib/tls/i686/cmov/libc.so.6
#8  0x00000000 in ?? ()
--------------------------------------------
second try:
above does not look like much so I used "gdb konqueror"  to produce a 
backtrace, copied the screen contents and pasted here:

msj@lptp:~$ gdb konqueror
GNU gdb 6.6-debian
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 "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/konqueror
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235269952 (LWP 7177)]
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
X Error: BadDevice, invalid or uninitialized input device 158
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 158
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1235269952 (LWP 7177)]
0xb7c1f610 in rawmemchr () from /lib/tls/i686/cmov/libc.so.6
(gdb) backtrace
#0  0xb7c1f610 in rawmemchr () from /lib/tls/i686/cmov/libc.so.6
#1  0xb7c14396 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0x00000000 in ?? ()
(gdb)   

---------------------------------
3rd try:
backtrace using  valgrind --log-file=konqcrash konqueror

from crashed konqueror backtrace screen I got the following which I screen 
captured and have pasted herewith:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents 
creation of proper backtraces, or the stack frame was seriously corrupted in 
the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
0x3805adec in ?? () from /lib/ld-linux.so.2
#0  0x3805adec in ?? () from /lib/ld-linux.so.2
#1  0x62370eec in ?? ()
#2  0x38aed2dc in ?? ()
#3  0x000000a2 in ?? ()
#4  0x38c03060 in ?? ()
#5  0x3804cb89 in ?? ()
#6  0x000000a2 in ?? ()
#7  0x38aed2dc in ?? ()
#8  0x62370eb8 in ?? ()
#9  0x62370eb0 in ?? ()
#10 0x00000008 in ?? ()
#11 0x62370e48 in ?? ()
#12 0x6235baa6 in ?? ()
#13 0x04c1b029 in ?? ()
#14 0xbeba2dac in ?? ()
#15 0x00000000 in ?? ()
----------------------------------------

the valgrind log file is attached.

--------------------------------

The files that cause konqueror to crash are provide by a financial management 
firm and as such contain sensitive estate information.  Will ask the firm to 
send me a test document that does not contain sensitive estate information, 
this request will take a few days as company is closed for the weekend.

Martin S-J.

On Friday 28 March 2008 18:53:25 Pino Toscano wrote:
[bugs.kde.org quoted mail]


Created an attachment (id=24113)
konqcrash.7399

Pino:
I just noticed that dolphin file manager (new to Kubuntu v7.1) also crashes 
when I mouse over a xenos PDFout file;
Note the same reference to libc.so.6 - is it possible that the libc.so.6 is at 
fault?

dolphin's backtrace is:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234606400 (LWP 8363)]
[KCrash handler]
#6  0xb6739610 in rawmemchr () from /lib/tls/i686/cmov/libc.so.6
#7  0xb672e396 in ?? () from /lib/tls/i686/cmov/libc.so.6
#8  0x00000000 in ?? ()


On Friday 28 March 2008 18:53:25 Pino Toscano wrote:
[bugs.kde.org quoted mail]

Just uploaded the latest upgrades for Kubuntu 7.10 :  upgrade consisted of 
three files related to PDF operation.   Konqueror and Dolphin no longer crash 
with "mouse over " a Xenos PDFout V3.8t file.

Thanks for your replies and to who ever fixed the item.

Martin Stanley-Jones

On Friday 28 March 2008 18:53:25 Pino Toscano wrote:
[bugs.kde.org quoted mail]

> ------- Additional Comments From pino kde org  2008-03-28 09:53 -------
> Can you please provide:
> a) an better backtrace, as described
> http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How
>_to_create_useful_crash_reports b) the document that makes konqueror crash
>
> Thanks.

The problem was in the Poppler library, and it was fixed in version 0.6.3.

*** This bug has been marked as a duplicate of 152710 ***