Support (#5) - cannot run SHM (#11) - Message List
Hi, there!
The command-line mode by running SH works well. However, the GUI mode by SHM doesn't. Here is the message:
SeismicHandler version 2.4h (05-May-2007), Copyright (C) 2006 Klaus Stammler, Seismological Observatory Graefenberg (SZGRF) of the Federal Institute for Geosciences and Natural Resources (BGR). SeismicHandler comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; see $SH_ROOT/doc/gpl.txt for details. *** buffer overflow detected ***: /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7a94da8] /lib/tls/i686/cmov/libc.so.6[0xb7a92eb0] /lib/tls/i686/cmov/libc.so.6(__strcpy_chk+0x44)[0xb7a92184] /usr/lib/libMrm.so.3(Idb__HDR_GetHeader+0x2b8)[0xb7ede018] /usr/lib/libMrm.so.3(UrmIdbOpenFileRead+0xec)[0xb7ee171c] /usr/lib/libMrm.so.3[0xb7ee2e76] /usr/lib/libMrm.so.3(Urm__OpenHierarchy+0x1ab)[0xb7ee322b] /usr/lib/libMrm.so.3(MrmOpenHierarchyPerDisplay+0x65)[0xb7ee23b5] /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world[0x804b5df] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb79ad775] /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world[0x804b1e1] ======= Memory map: ======== 08048000-08149000 r-xp 00000000 08:01 338439 /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world 08149000-0814a000 r--p 00100000 08:01 338439 /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world 0814a000-08165000 rw-p 00101000 08:01 338439 /home/ll/Soft/SH-SHM/shfiles/sh/source/motif/shm_world 08165000-081c4000 rw-p 08165000 00:00 0 09f1e000-09f60000 rw-p 09f1e000 00:00 0 [heap] b791f000-b792c000 r-xp 00000000 08:01 236705 /lib/libgcc_s.so.1 b792c000-b792d000 r--p 0000c000 08:01 236705 /lib/libgcc_s.so.1 b792d000-b792e000 rw-p 0000d000 08:01 236705 /lib/libgcc_s.so.1 b792e000-b7936000 r-xp 00000000 08:01 736019 /usr/lib/libXrender.so.1.3.0 b7936000-b7937000 r--p 00007000 08:01 736019 /usr/lib/libXrender.so.1.3.0 b7937000-b7938000 rw-p 00008000 08:01 736019 /usr/lib/libXrender.so.1.3.0 b7949000-b794b000 rw-p b7949000 00:00 0 b794b000-b794f000 r-xp 00000000 08:01 735995 /usr/lib/libXdmcp.so.6.0.0 b794f000-b7950000 rw-p 00003000 08:01 735995 /usr/lib/libXdmcp.so.6.0.0 b7950000-b7953000 r-xp 00000000 08:01 236794 /lib/libuuid.so.1.2 b7953000-b7954000 r--p 00002000 08:01 236794 /lib/libuuid.so.1.2 b7954000-b7955000 rw-p 00003000 08:01 236794 /lib/libuuid.so.1.2 b7955000-b7957000 r-xp 00000000 08:01 254136 /lib/tls/i686/cmov/libdl-2.9.so b7957000-b7958000 r--p 00001000 08:01 254136 /lib/tls/i686/cmov/libdl-2.9.so b7958000-b7959000 rw-p 00002000 08:01 254136 /lib/tls/i686/cmov/libdl-2.9.so b7959000-b7971000 r-xp 00000000 08:01 736568 /usr/lib/libxcb.so.1.1.0 b7971000-b7972000 r--p 00017000 08:01 736568 /usr/lib/libxcb.so.1.1.0 b7972000-b7973000 rw-p 00018000 08:01 736568 /usr/lib/libxcb.so.1.1.0 b7973000-b7974000 rw-p b7973000 00:00 0 b7974000-b7976000 r-xp 00000000 08:01 735984 /usr/lib/libXau.so.6.0.0 b7976000-b7977000 r--p 00001000 08:01 735984 /usr/lib/libXau.so.6.0.0 b7977000-b7978000 rw-p 00002000 08:01 735984 /usr/lib/libXau.so.6.0.0 b7978000-b797f000 r-xp 00000000 08:01 736013 /usr/lib/libXp.so.6.2.0 b797f000-b7980000 r--p 00006000 08:01 736013 /usr/lib/libXp.so.6.2.0 b7980000-b7981000 rw-p 00007000 08:01 736013 /usr/lib/libXp.so.6.2.0 b7981000-b7996000 r-xp 00000000 08:01 736009 /usr/lib/libXmu.so.6.2.0 b7996000-b7997000 rw-p 00015000 08:01 736009 /usr/lib/libXmu.so.6.2.0 b7997000-b7af3000 r-xp 00000000 08:01 254130 /lib/tls/i686/cmov/libc-2.9.so b7af3000-b7af4000 ---p 0015c000 08:01 254130 /lib/tls/i686/cmov/libc-2.9.so b7af4000-b7af6000 r--p 0015c000 08:01 254130 /lib/tls/i686/cmov/libc-2.9.so b7af6000-b7af7000 rw-p 0015e000 08:01 254130 /lib/tls/i686/cmov/libc-2.9.so b7af7000-b7afa000 rw-p b7af7000 00:00 0 b7afa000-b7b09000 r-xp 00000000 08:01 736015 /usr/lib/libXpm.so.4.11.0 b7b09000-b7b0a000 rw-p 0000f000 08:01 736015 /usr/lib/libXpm.so.4.11.0 b7b0a000-b7b0b000 rw-p b7b0a000 00:00 0 b7b0b000-b7b12000 r-xp 00000000 08:01 735976 /usr/lib/libSM.so.6.0.0 b7b12000-b7b13000 r--p 00006000 08:01 735976 /usr/lib/libSM.so.6.0.0 b7b13000-b7b14000 rw-p 00007000 08:01 735976 /usr/lib/libSM.so.6.0.0 b7b14000-b7b29000 r-xp 00000000 08:01 735945 /usr/lib/libICE.so.6.3.0 b7b29000-b7b2a000 rw-p 00014000 08:01 735945 /usr/lib/libICE.so.6.3.0 b7b2a000-b7b2c000 rw-p b7b2a000 00:00 0 b7b2c000-b7c16000 r-xp 00000000 08:01 735Abort
-
Message #26
Hi Li,
please describe your system more in detail (hard- and software). Please check the compiler run for relevant messages.
Which version of SHM are you using?
Marcus
PS: Please use WikiFormatting#PreformattedText for pasted text for preserving original formatting (I did edit your original post too).
08/11/09 16:13:55-
Message #27
Hi, Marcus,
I downloaded the tar files from http://www.seismic-handler.org/portal/wiki/AllDownloads. They should be the latest version. I used the install script provided to install SH-SHM following the instructions at http://www.seismic-handler.org/portal/wiki/ShmInstallUbuntu step by step.
I installed SH-SHM under Ubuntu 8 on my PC successfully. But it doesn't work on my Thinkpad Notebook. The OS is Ubuntu 9. The compliers include gcc and gfortran of version 4.3.3. I'll paste the compling information later.
Thanks for your reply.
li08/12/09 04:09:42 -
Message #28
Hi Li,
maybe the installation instructions for Ubuntu are not valid for Ubuntu 9 - personally I'm stuck with 8.04. ;) I'll try it in a virtual machine.
Marcus
08/18/09 07:24:15-
Message #29
Hello Li,
I can confirm this bug. It's filed under ticket number 12. I hope, a solution can be found soon.
Marcus
08/19/09 15:04:15-
Message #31
Hi,
Is the bug in the distribution upgrade or the kernel upgrade? I have an ubuntu derivative (Mint7) that I can downgrade (to Mint5), but would like to upgrade the kernel and drivers to match my machine (a desktop Dell inspiron 530 with dual core quad).
Thanks, Virginia
VStern10/19/09 19:12:55-
Message #32
Hi Virginia,
in fact it's a bug in Seismic Handler Motif version that's hard to catch. By introducing new compiler features the os detects this error and shuts down SHM.
So it's not a kernel issue nor a distribution problem, just a unfavourable situation... :(
We did not locate the bug in SHM yet, so I'll try to find a way to disable the new compiler features (less-than-ideal solution, but maybe the fastest).
Marcus
10/20/09 08:56:57-
Message #33
Hi Marcus,
I've installed ubuntu 8.04 but now have an error:
"/usr/share/sh/sh/source/motif/shm_world: Command not found."
I've saved the installation verbage if that is helpful.
Regards, Virginia
VStern10/20/09 18:59:14-
Message #34
Hi Virginia,
SHM runs definitely under Ubuntu 8.04, if you follow the installation instructions. Only later versions show the compiler issue.
Marcus
10/21/09 10:29:32-
Message #35
Hi Marcus,
Sorry, it's taken me so long to reply, but I've tried a lot of different configurations to get around the ubuntu issues.
Yes, SHM works on older versions of Ubuntu-clones, but I've had some problems with these versions of ubuntu not working in /VirtualBox/. On Debian lenny, xedit is missing, so I couldn't use the SHM versions meant for ubuntu. The deb-packages by Jens Oeser work on Debian lenny, but I have a question regarding it's interaction with LocSAT. In shsetup there are two paths set for locsat:
setenv SH_LOCSAT /home/klaus/lcs & setenv SH_LOCSAT_EXEC $SH_UTIL/LocSAT
Obviously, there is no such folder as "/home/klaus/lcs" in my directory, but what should I replace it with and what table is locsat looking for in that folder?
I ask this because the error that I got when I tried to run locsat was something like: cannot open /home/klaus/lcs/****.TBL (sorry - If you need it verbatm I took a ksnapshot and will send that) as well as: could not find /home/virg/shscratch/locsat_r.txt
other files were made in shscratch such as locsat_c & locsat_d, but not locsat_r.
Thanks for your help, Virginia
VStern12/02/09 17:14:17-
Message #36
We have nearly no experience with VirtualBox?, so I cannot help you in that case (we use mostly VmWare?, see AllDownloads). If you solve this issue please write a wiki page here, so that other users can profit from your efforts!
You can edit the pathnames for LocSat? in shsetup - but there's one pitfall: The pathname to LocSat? must not be longer than 32 chars (otherwise use symbolic links).
locsat_r.txt will be created by LocSat?. If the binary cannot be found, SHM fails to lookup this file.
Marcus
12/03/09 08:29:24
-
-
-
-
-
-
-
-