VMD-L Mailing List

From: Luis Rosales (ludwig_at_biomedicas.unam.mx)
Date: Tue Nov 30 2004 - 19:10:11 CST

Hi:

I just ran vmd 1.8.3.31 with the new variable and it ran without any
problems!!!
Just for the list, in case that anyone is interested, the new varible is
defined as:

if ($?VMDMSMSUSEFILE == "0") then
  setenv VMDMSMSUSEFILE on
endif

As for the debugger, I ran GNU debbuger as you tellme and the output for it
is:

Arioco_at_ruiz2 12% gdb msms.i86Linux2.2.5.5

(gdb) run -socketPort 1357
Starting program: /home/arioco/bin/MSMS/msms.i86Linux2.2.5.5 -socketPort
1357

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()

(gdb) where
#0 0x00000000 in ?? ()
#1 0x007c9e98 in ?? ()
#2 0x00868180 in ?? ()
#3 0x00b27dce in ?? ()
#4 0x006d66be in ?? ()
#5 0xfeffec60 in ?? ()
#6 0x080a60ae in _dl_lookup_versioned_symbol ()
#7 0x00730ea8 in ?? ()
#8 0x00000000 in ?? ()

However, ldd reposrts the executable as "not a dynamic executable".

I will send the problem report the msms team (I assume thatīs Michael
Sanner) right now.

Thanks,

Luis

> -----Mensaje original-----
> De: John Stone [mailto:johns_at_ks.uiuc.edu]
> Enviado el: Martes, 30 de Noviembre de 2004 16:35
> Para: Luis Rosales
> CC: vmd-l_at_ks.uiuc.edu; 'Brian Bennion'
> Asunto: Re: vmd-l: MSMS variable
>
>
> Luis,
> If MSMS crashes when used with the socketPort option, that
> completely explains the reason VMD fails to talk to it. There are
> two ways around this:
>
> 2) Run MSMS manually in a debugger and report the crash to the
> MSMS authors so they can fix it. Like this:
> gdb msms.whatever.you.named.it
> run -socketPort 1357
> ...then, when it crashes:
> where
> Then email the 'where' output to the MSMS team along with
> the output of 'ldd msms.whatever.you.named.it' so they can
> see what dynamic link libraries your MSMS is linking against.
> They'll probably need to know which Linux distro you're
> running too.
>
> John Stone