SIGSEGV crash

[Bill Suit]

I get a SIGSEGV crash message upon opening and closing kmm2. I do not lose any
functionality, but the message has finally become annoying enough to put it
out here. The back trace is:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7f204c2a8700 (LWP 18790)]
[KCrash handler]
#5  0x00007f204be3681a in QMapPrivate<void*, _CheckMemoryEntry>::find (
    this=0x2d9e1e0, k=@0x7fff542dfec8) at /usr/qt/3/include/qmap.h:503
#6  0x00007f204be36f4e in QMap<void*, _CheckMemoryEntry>::find (this=0xe00a68,
    k=@0x7fff542dfec8) at /usr/qt/3/include/qmap.h:696
#7  0x00007f204be35b9d in operator delete[] (p=0x3447310)
    at mymoneyutils.cpp:204
#8  0x00007f2046ad86f7 in QStringData::deleteSelf ()
   from /usr/qt/3/lib64/libqt-mt.so.3
#9  0x0000000000593258 in ~QString (this=0x343e2d8)
    at /usr/qt/3/include/qstring.h:848
#10 0x00007f204be369f9 in ~_CheckMemoryEntry (this=0x343e2c0)
    at mymoneyutils.h:109
#11 0x00007f204be36a15 in ~QMapNode (this=0x343e2a0)
    at /usr/qt/3/include/qmap.h:84
#12 0x00007f204be37013 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
    this=0x2d9e1e0, p=0x343e2a0) at /usr/qt/3/include/qmap.h:490
#13 0x00007f204be36ff0 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
    this=0x2d9e1e0, p=0x343e0e0) at /usr/qt/3/include/qmap.h:488
#14 0x00007f204be37052 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
    this=0x2d9e1e0) at /usr/qt/3/include/qmap.h:477
#15 0x00007f204be3716b in QMap<void*, _CheckMemoryEntry>::clear
(this=0xe00a68)
    at /usr/qt/3/include/qmap.h:810
#16 0x00007f204be371df in _CheckMemory::Restart (this=0xe00a60)
    at mymoneyutils.h:136
#17 0x00007f204be35c32 in _CheckMemory_End () at mymoneyutils.cpp:157
#18 0x00000000005e8978 in _cleanup () at main.cpp:81
#19 0x00007f2042f25aa9 in exit () from /lib/libc.so.6
#20 0x00007f2042f104ab in __libc_start_main () from /lib/libc.so.6
#21 0x000000000058f039 in _start ()

Thanks for any help clearing this up.

Bill

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

[Bill Suit]

Thanks Alvaro and Allan. Compiling without the memory checker seems to have
resolved the problem. Don't know what changed, as I've been compiling with
memory checker for several years. Oh well.

On Wednesday 11 November 2009 07:36:39 Alvaro Soliverez wrote:

> Hello Bill,
> I take it you are using a compiled version which has the leak memory
> checker turned on. Is that correct?
> If so, compile again with the checker turned off.
>
> If not, please inform which version you are using, your distro and install
> package.
>
> Regards,
> Alvaro
>
> On Wed, Nov 11, 2009 at 4:24 AM, Bill Suit <bsuit@...> wrote:
> > I get a SIGSEGV crash message upon opening and closing kmm2. I do not
> > lose any
> > functionality, but the message has finally become annoying enough to put
> > it out here. The back trace is:

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

Hello Bill,
I take it you are using a compiled version which has the leak memory checker turned on. Is that correct?
If so, compile again with the checker turned off.

If not, please inform which version you are using, your distro and install package.

Regards,
Alvaro

On Wed, Nov 11, 2009 at 4:24 AM, Bill Suit <bsuit@...> wrote:

I get a SIGSEGV crash message upon opening and closing kmm2. I do not lose any
functionality, but the message has finally become annoying enough to put it
out here. The back trace is:

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

[allan anderson]

Bill Suit wrote:

> I get a SIGSEGV crash message upon opening and closing kmm2. I do not lose any
> functionality, but the message has finally become annoying enough to put it
> out here. The back trace is:
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread 0x7f204c2a8700 (LWP 18790)]
> [KCrash handler]
> #5  0x00007f204be3681a in QMapPrivate<void*, _CheckMemoryEntry>::find (
>     this=0x2d9e1e0, k=@0x7fff542dfec8) at /usr/qt/3/include/qmap.h:503
> #6  0x00007f204be36f4e in QMap<void*, _CheckMemoryEntry>::find (this=0xe00a68,
>     k=@0x7fff542dfec8) at /usr/qt/3/include/qmap.h:696
> #7  0x00007f204be35b9d in operator delete[] (p=0x3447310)
>     at mymoneyutils.cpp:204
> #8  0x00007f2046ad86f7 in QStringData::deleteSelf ()
>    from /usr/qt/3/lib64/libqt-mt.so.3
> #9  0x0000000000593258 in ~QString (this=0x343e2d8)
>     at /usr/qt/3/include/qstring.h:848
> #10 0x00007f204be369f9 in ~_CheckMemoryEntry (this=0x343e2c0)
>     at mymoneyutils.h:109
> #11 0x00007f204be36a15 in ~QMapNode (this=0x343e2a0)
>     at /usr/qt/3/include/qmap.h:84
> #12 0x00007f204be37013 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
>     this=0x2d9e1e0, p=0x343e2a0) at /usr/qt/3/include/qmap.h:490
> #13 0x00007f204be36ff0 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
>     this=0x2d9e1e0, p=0x343e0e0) at /usr/qt/3/include/qmap.h:488
> #14 0x00007f204be37052 in QMapPrivate<void*, _CheckMemoryEntry>::clear (
>     this=0x2d9e1e0) at /usr/qt/3/include/qmap.h:477
> #15 0x00007f204be3716b in QMap<void*, _CheckMemoryEntry>::clear
> (this=0xe00a68)
>     at /usr/qt/3/include/qmap.h:810
> #16 0x00007f204be371df in _CheckMemory::Restart (this=0xe00a60)
>     at mymoneyutils.h:136
> #17 0x00007f204be35c32 in _CheckMemory_End () at mymoneyutils.cpp:157
> #18 0x00000000005e8978 in _cleanup () at main.cpp:81
> #19 0x00007f2042f25aa9 in exit () from /lib/libc.so.6
> #20 0x00007f2042f104ab in __libc_start_main () from /lib/libc.so.6
> #21 0x000000000058f039 in _start ()
>
> Thanks for any help clearing this up.
>
> Bill
>
> ------------------------------------------------------------------------------

I know next to nothing about this, but I wonder have you enabled the
memleak check in .configure?  If so, try removing it.

allan

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

[Thomas Baumgart]

On Wednesday 11 November 2009 09:51:48 Bill Suit wrote:
> Thanks Alvaro and Allan. Compiling without the memory checker seems to have
> resolved the problem. Don't know what changed, as I've been compiling with
> memory checker for several years. Oh well.

This happened to me now and then. Mostly influenced by compiler version and
options. Nevertheless, the memory leak checker was great to have in the
beginning. Now we have valgrind and can safely turn off our own little
helper.


--

Regards

Thomas Baumgart

GPG-FP: E55E D592 F45F 116B 8429   4F99 9C59 DB40 B75D D3BA
-------------------------------------------------------------
There are two rules for success in life:
Rule 1: Don't tell people everything you know.
-------------------------------------------------------------


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer