namd crash: Signal: segmentation violation

From: Leandro Martínez (
Date: Wed May 23 2007 - 14:30:05 CDT

Now I got them. Running locally (++local +p2) or
in two nodes (4 cpus), the "where" for the core
created returns:

(gdb) where
#0 0x00002b6b8a40a737 in kill () from /lib/
#1 0x00002b6b8a2d7381 in EF_newFrame () from /usr/lib/
#2 0x00002b6b8a2d7b41 in EF_delFrame () from /usr/lib/
#3 0x00002b6b8a40ca65 in exit () from /lib/
#4 0x000000000040ad9e in socket_error_in_poll (code=93620,
msg=0x40de13 "Socket closed before recv.")
    at charmrun.c:1699
#5 0x0000000000403b26 in skt_recvN (hSocket=4, buff=0x7fff208ed680,
nBytes=16) at sockRoutines.c:424
#6 0x0000000000403edc in ChMessageHeader_recv (fd=4,
dst=0x7fff208ed680) at sockRoutines.c:563
#7 0x000000000040acb7 in req_serve_client (fd=4) at charmrun.c:1656
#8 0x000000000040b044 in req_poll () at charmrun.c:1745
#9 0x000000000040ba58 in main (argc=5, argv=0x7fff208ee0d8,
envp=0x7fff208ee108) at charmrun.c:2084

This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:44:43 CST