#296 x86_64 only: Crash when Dialog box closes

open
nobody
5
2008-07-14
2008-07-14
No

Test program at
http://staff.chess.cornell.edu/~schuller/080714ltbug.tar.gz
(also attached)

Open a dialog box with Bulletinboard containing a label and two pushbottons. Choose button "YES" or "NO." When compiled with lesstif 0.95.0-25.fc9.x86_64, application crashes with Segmentation fault.

When program is compiled with
lesstif-0.95.0-25.fc9.i386 or openmotif-2.3.0-0.3.fc8.ccrma.x86_64, dialog box shuts down.

May involve XmNautoUnmanage. On openmotif, commenting out the XmNautoUnmanage line causes program to crash in same way as with 64 bit lesstif. With 32 bit lesstif, commenting out that line has no effect (program does not crash either way)

Fedora 9 2.6.25.9-76.fc9.x86_64
lesstif-0.95.0-25.fc9.x86_64
lesstif-devel-0.95.0-25.fc9.x86_64
also involved for comparison:
lesstif-0.95.0-25.fc9.i386
openmotif-2.3.0-0.3.fc8.ccrma.x86_64

djs@bridgedec.chess.cornell.edu

Discussion

  • Crystal Cowboy

    Crystal Cowboy - 2008-07-14

    Test code

     
    Attachments
  • Paul Gevers

    Paul Gevers - 2009-04-29

    I am new to lesstif, but I am going to try and clean up the source code a little bit. The debian bug tracker already includes a patch which I think will fix this bug. Are you in the position to test it?

    See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503361#15

     
  • Nobody/Anonymous

    I am not currently in a situation for testing. I have lesstif-0.95.0-26 and lesstif-devel-0.95.0-26 installed from RPM on a Fedora 9 system.

    I suppose I could install source code for testing purposes, but I do not see anything about a git tree, and the SourceForge download menu offers me something labeled 0.95.0 (no minor version noted) which was last updated in 2006. If you would like me to do some testing, make it easier for me.

    Alternatively, I did attach source code so that you can duplicate the problem yourself.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks