Having built Ishmail 1.9.12 as documented in my previous bug report, I am finding that *whenever*
I send a message (using the send/close button), Ishmail emits the message and then core dumps
before closing the window.
I'm experiencing similar behavior, although not every time I send mail. In my case, ishmail is receiving a signal while in a memory-allocation routine; the signal handler calls another function which tries to call another memory-allocation function. The mem-allocation routines aren't reentrant so this causes a crash.
Could you use a debugger to produce a backtrace from the core file? I'd like to rule out the possibility that your problem is from something else.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's the backtrace from the core dump. I've rebuilt the entire Ishmail tree with -DHPUX.
#0 0x1c785c in SendWinP::Send (this=0x402e7390, closing=1 '\001') at SendFile.C:502
#1 0x1c6958 in SendWinP::DoSendClose (This=0x402e7390) at SendFile.C:207
#2 0xc095ec3c in XtCallCallbacks ()
#3 0xd4fa0 in ButtonMgrC::DoActivate (pb=0x0, callData=0x4033a6ed)
at ButtonMgrC.C:299
#4 0xc095eda4 in XtCallCallbackList ()
#5 0xc1dbf3f4 in ActivateCommon ()
#6 0xc1dbf138 in Activate ()
#7 0xc0995634 in HandleActions ()
#8 0xc0996004 in HandleComplexState ()
#9 0xc0996110 in _XtTranslateEvent ()
#10 0xc096cac8 in XtDispatchEventToWidget ()
#11 0xc096d534 in _XtDefaultDispatcher ()
#12 0xc096daac in XtDispatchEvent ()
#13 0xc096df68 in XtAppMainLoop ()
#14 0x204320 in main (argc=1, argv=0x7b03ac7c) at main.C:153
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm experiencing similar behavior, although not every time I send mail. In my case, ishmail is receiving a signal while in a memory-allocation routine; the signal handler calls another function which tries to call another memory-allocation function. The mem-allocation routines aren't reentrant so this causes a crash.
Could you use a debugger to produce a backtrace from the core file? I'd like to rule out the possibility that your problem is from something else.
Try to recompile hgl/HalAppC.C and hgl/MemMap.C with -DHPUX and see if it makes any change.
Rebuilding hgl/HalAppC and hgl/MemMap with -DHPUX did *NOT* fix the problem.
Here's the backtrace from the core dump. I've rebuilt the entire Ishmail tree with -DHPUX.
#0 0x1c785c in SendWinP::Send (this=0x402e7390, closing=1 '\001') at SendFile.C:502
#1 0x1c6958 in SendWinP::DoSendClose (This=0x402e7390) at SendFile.C:207
#2 0xc095ec3c in XtCallCallbacks ()
#3 0xd4fa0 in ButtonMgrC::DoActivate (pb=0x0, callData=0x4033a6ed)
at ButtonMgrC.C:299
#4 0xc095eda4 in XtCallCallbackList ()
#5 0xc1dbf3f4 in ActivateCommon ()
#6 0xc1dbf138 in Activate ()
#7 0xc0995634 in HandleActions ()
#8 0xc0996004 in HandleComplexState ()
#9 0xc0996110 in _XtTranslateEvent ()
#10 0xc096cac8 in XtDispatchEventToWidget ()
#11 0xc096d534 in _XtDefaultDispatcher ()
#12 0xc096daac in XtDispatchEvent ()
#13 0xc096df68 in XtAppMainLoop ()
#14 0x204320 in main (argc=1, argv=0x7b03ac7c) at main.C:153