Bug 52458 - kmail segfaults and cores on startup
Summary: kmail segfaults and cores on startup
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Solaris
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-31 17:20 UTC by Misty Stanley-Jones
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Misty Stanley-Jones 2002-12-31 17:20:10 UTC
Version:           Don't know (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.2 
OS:          Solaris

[ms126519@starkitty ms126519]$ kmail
Segmentation Fault (core dumped)
[ms126519@starkitty ms126519]$ file core
core:           ELF 32-bit MSB core file SPARC Version 1, from 'kmail'
[ms126519@starkitty ms126519]$ mdb core
Loading modules: [ libc.so.1 libthread.so.1 ld.so.1 ]
> $c
libkmailpart.so.1.0.0`_ZN7QShared3refEv+0x10(0, 0, 558, fed09f38, fec2bde8, 2)
libqt-mt.so.3.1.1`_ZN7QStringC1ERKS_+0x24(ff0326c0, fd942f3c, 0, 0, 0, 0)
libkmailpart.so.1.0.0`_ZN10KMIdentityC1ERK7QStringS2_S2_S2_S2_+0x30(ff0326bc,
fd942f3c, fd942f3c, fd942f3c, fd942f3c, fd942f3c)
libkmailpart.so.1.0.0`_Z41__static_initialization_and_destruction_0ii+0xc4(1,
ffff, 0, 0, 0, 0)
libkmailpart.so.1.0.0`_GLOBAL__I__ZN9SignatureC2Ev+0x10(fee2ab10, ff0178e0, 0, 0
, 0, 0)
0xfeefc618(ff017a58, 0, 0, 0, 0, 0)
libkmailpart.so.1.0.0`_init+0xc(0, ff3b0890, 1, ff3f66cc, 1668628, fe880394)
ld.so.1`call_init+0x150(80000, ffdfffff, ff3f66cc, ff3f6168, 200000, 0)
ld.so.1`elf_bndr+0x348(1, ff3f7c80, 241b, fd2047b0, fec16f78, 5)
ld.so.1`elf_rtbndr+0x10(fd5bffc8, 21b78, 0, 796c6500, 81010100, ff00)
0xfd8e2c54(21b78, fd837770, 188, 0, fd6a8ec0, 2)
libqt-mt.so.3.1.1`_ZN6QGDict10look_asciiEPKcPvi+0x2a4(20d60, fd8c68c0, fd6a8ec0
, 1, 1, 0)
libqt-mt.so.3.1.1`_ZN10QAsciiDictIvE6insertEPKcPKv+0x20(20d60, fd8c68c0,
fd6a8ec0, 1, 0, 0)
libqt-mt.so.3.1.1`_ZN18QMetaObjectCleanUpC1EPKcPFP11QMetaObjectvE+0x94(fd9432a4
, fd8c68c0, fd6a8ec0, 0, 0, 0)
libqt-mt.so.3.1.1`_Z41__static_initialization_and_destruction_0ii+0x64(1, ffff,
0, 0, 0, 0)
libqt-mt.so.3.1.1`_GLOBAL__I__ZNK11QMotifStyle9classNameEv+0x10(fd6a91a4,
fd90b06c, 0, 0, 0, 0)
0xfd6a9220(fd90b2fc, 0, 0, 0, 0, 0)
libqt-mt.so.3.1.1`_init+0xc(0, fe880394, 1, e, ff3cc1d0, 0)
ld.so.1`call_init+0x150(80000, ffdfffff, ff3f66cc, ff3f6168, 200000, 0)
ld.so.1`setup+0xf6c(ff3f6080, 0, ff3f6158, 0, ff3b0214, 10094)
ld.so.1`_setup+0x368(a, a, ffbfffcd, ffbfffdd, 0, ff3d6a18)
ld.so.1`_rt_boot+0x88(0, 0, 0, 0, 0, 0)
0(0, 0, 0, 0, 0, 0)

I will keep the core around if there are additional commands you would like me to run on it.  Though it is very easy to get a new one -- it crashes every time.
Comment 1 Ingo Klöcker 2003-01-01 17:06:05 UTC
Subject: Re:  New: kmail segfaults and cores on startup

Please send us the backtrace you get when KMail crashes. If you don't 
get a backtrace from the KDE Crash Manager then please run KMail in 
gdb. To get the backtrace do this:
Run KMail in gdb with
> gdb kmail
(gdb) run --nofork

Make KMail crash

Create a backtrace with
(gdb) bt

Comment 2 Misty Stanley-Jones 2003-01-01 19:35:40 UTC
Subject: Re:  kmail segfaults and cores on startup         

I did include a stack trace, but not with gdb.  gdb is not a standard
utility on Solaris, and I will have to compile it.  I was hoping that the
backtrace I did include (from gdb) would be of some help.  Tomorrow I will
install gdb and get you another crash dump.

On Wed, 1 Jan 2003, Ingo Kl
Comment 3 Misty Stanley-Jones 2003-03-06 19:59:20 UTC
I think it's resolved by a newer build. 
Comment 4 Helio Chissini de Castro 2003-06-09 16:44:21 UTC
Still crashing on CVS HEAD and 3.1.2 and Linux ix86 arch. 
Unusual compilation flags used: 
--disable-debug --enable-mt --with-fast-malloc=full 
Comment 5 Ingo Klöcker 2003-06-10 00:47:50 UTC
Subject: Re:  kmail segfaults and cores on startup

Hi Helio!

We can't do anything about crashes which we obviously can't reproduce 
because else this bug would have been fixed long ago without a useful 
backtrace. So please re-compile with --enable-debug=full and send us 
the backtrace you get.

Regards,
Ingo

Comment 6 Helio Chissini de Castro 2003-06-13 22:55:26 UTC
Back to fixed, since i did a mistake on report this one.. 
My apologies for all :-)