Experimental Physics and
| |||||||||||||||
|
I am running Ubuntu 7.10 on 64bit box and I am having problems with running Alarm handler (tried different versions to same results, 1.2.16 and 1.2.23, also used different EPICS, 3.14.7 and 3.14.8.2 ). Although it starts fine if you run it without any arguments it exits with a Segmentation fault when you load a .alhConfig file. From gdb we got this output: pmedvescek@CSL146:~/workspace$ gdb alh GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /opt/epics/extensions/bin/linux-x86/alh [Thread debugging using libthread_db enabled] [New Thread 47894097469072 (LWP 7522)] no XML! [New Thread 1073875280 (LWP 7526)] [New Thread 1074141520 (LWP 7527)] [New Thread 1074407760 (LWP 7528)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47894097469072 (LWP 7522)] 0x00002b8f3437d4e2 in _XtCountVaList () from /usr/lib/libXt.so.6 (gdb) bt #0 0x00002b8f3437d4e2 in _XtCountVaList () from /usr/lib/libXt.so.6 #1 0x00002b8f3437c288 in XtVaCreateManagedWidget () from /usr/lib/libXt.so.6 #2 0x0000000000419c27 in createRuntimeWindow (area=0x8bb970) at ../axRunW.c:170 #3 0x000000000041788f in setupConfig ( filename=0x69b8c0 "/home/pmedvescek/workspace/OD-ASPPX2/OPI/main.alhConfig", program=1, areaOld=0x0) at ../axArea.c:254 #4 0x000000000041dcb2 in fileSetup ( filename=0x69b8c0 "/home/pmedvescek/workspace/OD-ASPPX2/OPI/main.alhConfig", area=0x0, fileType=0, programId=1, widget=0x689ca0) at ../file.c:557 #5 0x000000000041d858 in fileSetupCallback (widget=0x689ca0, client_data=0, cbs=0x7fff773ffbe0) at ../file.c:426 #6 0x00002b8f34344a8f in XtCallCallbackList () from /usr/lib/libXt.so.6 #7 0x00002b8f34042bfb in ?? () from /usr/lib/libXm.so.2 #8 0x00002b8f34344a8f in XtCallCallbackList () from /usr/lib/libXt.so.6 #9 0x00002b8f3406cd87 in ?? () from /usr/lib/libXm.so.2 #10 0x00002b8f3406d673 in ?? () from /usr/lib/libXm.so.2 #11 0x00002b8f340486df in _XmDispatchGadgetInput () from /usr/lib/libXm.so.2 #12 0x00002b8f3405fb9a in _XmGadgetActivate () from /usr/lib/libXm.so.2 #13 0x00002b8f3437a1ae in ?? () from /usr/lib/libXt.so.6 #14 0x00002b8f3437a927 in _XtTranslateEvent () from /usr/lib/libXt.so.6 #15 0x00002b8f3435256e in XtDispatchEventToWidget () from /usr/lib/libXt.so.6 #16 0x00002b8f34352c70 in ?? () from /usr/lib/libXt.so.6 #17 0x00002b8f34351d1b in XtDispatchEvent () from /usr/lib/libXt.so.6 #18 0x00002b8f34351e95 in XtAppMainLoop () from /usr/lib/libXt.so.6 #19 0x0000000000410b9e in main (argc=1, argv=0x7fff77400658) at ../alh.c:103 There seems to be some problems with libXt and on google I found some old discussions about similar problems people were having on 64bit machines. Since not being a vey experinced linux or EPICS user I am not 100% sure this is related but it sure looks familiar. Please see links below: http://lists.xastir.org/pipermail/xastir/2004-October/006431.html http://lists.debian.org/debian-multimedia/2006/10/msg00021.html Has anyone already experienced (and maybe solved) this issue? Any help will be deeply appreciated. Cheers, Peter.
| ||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |