Bug 505546 - Lesstif crash
Summary: Lesstif crash
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: lesstif
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-12 11:50 UTC by Mark van Rossum
Modified: 2009-08-03 09:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-03 09:49:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark van Rossum 2009-06-12 11:50:12 UTC
Description of problem:
I think I have discovered a problem with lesstif for 64bits.

I use a self-compiled version of xmgr (plotting program).
Works fine with FC 11 on 32 bits, but not on 64 bits.
Whenever I do Plot=>Symbols it crashes.

Version-Release number of selected component (if applicable):
Latest FC11 

How reproducible:
Always on 64 bit, never on 32 bit.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

(gdb) run
Starting program: /usr/local/bin/xmgr

Program received signal SIGSEGV, Segmentation fault.
XrmStringToQuark (name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>)
    at Quarks.c:363
363         for (tname = (char *)name; (c = *tname++); )

(gdb) backtrace
#0  XrmStringToQuark (
    name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>) at Quarks.c:363
#1  0x00000030f8c1c283 in xtWidgetAlloc (widget_class=<value optimized out>,
    parent_constraint_class=<value optimized out>, parent=0x7e8fc0,
    name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>, args=0x0,
    num_args=592, typed_args=0x0, num_typed_args=0) at Create.c:304
#2  0x00000030f8c1c4d3 in xtCreate (name=<value optimized out>,
    class=<value optimized out>, widget_class=0x3da137cd80,
    parent=<value optimized out>, default_screen=<value optimized out>,
    args=<value optimized out>, num_args=0, typed_args=0x0, num_typed_args=0,
    parent_constraint_class=0x3da137dbe0,
    post_proc=0x30f8c1bd40 <widgetPostProc>) at Create.c:357
#3  0x00000030f8c1cfca in _XtCreateWidget (
    name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>,
    widget_class=0x3da137cd80, parent=0x7e8fc0, args=0x0, num_args=0,
    typed_args=0x0, num_typed_args=0) at Create.c:563
#4  0x00000030f8c1d3ee in XtCreateWidget (
 name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>,
    widget_class=0x3da137cd80, parent=0x7e8fc0, args=0x0, num_args=0)
    at Create.c:582
#5  0x0000003da10c5cf4 in XmCreatePushButton (parent=0x7e8fc0,
    name=0x7fff00000000 <Address 0x7fff00000000 out of bounds>, arglist=0x0,
    argcount=0) at PushB.c:1535
#6  0x00000000004797a1 in CreatePanelChoice0 (parent=0x7e8730,
    labelstr=0x4afa75 " ", ncols=<value optimized out>, nchoices=47)
    at motifutils.c:173
#7  0x00000000004920e8 in define_symbols_popup (w=<value optimized out>,
    client_data=<value optimized out>, call_data=<value optimized out>)
    at symwin.c:431
#8  0x00000030f8c139df in XtCallCallbackList (widget=0x7a4bc0,
    callbacks=0x7a4850, call_data=0x7fffffffd0e0) at Callback.c:617
#9  0x0000003da10c4302 in ButtonUp (w=0x7a4bc0, event=0x7fffffffd6e0,
    params=<value optimized out>, num_params=<value optimized out>)
    at PushB.c:1331
#10 0x00000030f8c4b17d in HandleActions (w=<value optimized out>,
    event=0x7fffffffd6e0, stateTree=<value optimized out>,
    accelWidget=<value optimized out>, procs=<value optimized out>,
    actions=0x30f8e634a0) at TMstate.c:636
#11 0x00000030f8c4b2dc in HandleSimpleState (w=<value optimized out>,
    tmRecPtr=<value optimized out>, curEventPtr=0x7fffffffd290)
    at TMstate.c:875
#12 0x00000030f8c4bc67 in _XtTranslateEvent (w=<value optimized out>,
    event=<value optimized out>) at TMstate.c:1093
#13 0x00000030f8c21f83 in XtDispatchEventToWidget (widget=0x7a4bc0,
    event=0x7fffffffd6e0) at Event.c:898
#14 0x00000030f8c2281b in _XtDefaultDispatcher (event=0x7fffffffd6e0)
    at Event.c:1359
#15 0x00000030f8c21704 in XtDispatchEvent (event=0x0) at Event.c:1415
#16 0x00000030f8c218ab in XtAppMainLoop (app=0x70d0e0) at Event.c:1552
#17 0x000000000049c929 in do_main_winloop () at xmgr.c:1754
#18 0x0000000000406cab in do_main_loop () at main.c:1140



As said this program works fine under 32 bits, so I suspect lesstif rather than xmgr.

Comment 1 Hans de Goede 2009-06-12 11:57:02 UTC
Hi,

Not sure when I'll have the time to look into this, I'm afraid. Anyways for
when I do find the time I'll need the following info:

1) Location of the sources of xmgr
2) Information on how you compiled it (configure / Makefile settings used)
3) Have I understood correctly that it crashes immediately on startup ?

Comment 2 Mark van Rossum 2009-06-12 12:27:44 UTC
Hi

I have put the source on

http://homepages.inf.ed.ac.uk/mvanross/xmgr-4.1.2.tar.gz

./configure; make


The crash only happens after selecting, Plot => Symbols

I'm happy to help out further if I can...

Comment 3 Joachim Frieben 2009-08-03 08:59:58 UTC
I suggest you verify your observation after installing grace-5.1.22-4.fc11.x86_64 which is the official Fedora package of the application which you are referring to. Its ancient incarnation xmgr-4.1.2 is completely outdated (more than 10 years old)!

Comment 4 Joachim Frieben 2009-08-03 09:12:47 UTC
This is -not- a lesstif issue: I have built xmgr-4.1.2 on an x86_64 system against official Open Motif 2.3.2, and also in this case, xmgr* crashes when opening "Plot > Symbols...":

  "Oops! Got SIGSYS. Please use "Help/Comments" to report the bug."

Accordingly, this bug should be closed as NOTABUG.

Comment 5 Mark van Rossum 2009-08-03 09:24:41 UTC
(In reply to comment #4)
> This is -not- a lesstif issue: I have built xmgr-4.1.2 on an x86_64 system
> against official Open Motif 2.3.2, and also in this case, xmgr* crashes when

Did you try on 32bit with Open Motif as well?


> Accordingly, this bug should be closed as NOTABUG.  

Not so quick. Isn't a program that works well on 32bit, supposed to work on
64 bit as well?

Maybe it is not a lesstif bug though...

Comment 6 Hans de Goede 2009-08-03 09:49:02 UTC
(In reply to comment #5)
> 
> > Accordingly, this bug should be closed as NOTABUG.  
> 
> Not so quick. Isn't a program that works well on 32bit, supposed to work on
> 64 bit as well?
> 

It is, but if it does not even work with the official motif it is not a lesstif issue but an issue with the program itself.

> Maybe it is not a lesstif bug though...  

Exactly, closing as not a bug.


Note You need to log in before you can comment on or make changes to this bug.