Author Topic: feap running  (Read 3077 times)

peterattalla4

  • New Member
  • *
  • Posts: 3
feap running
« on: May 01, 2023, 05:40:26 AM »
while running feap
this error massage appears for me
Backtrace for this error:
#0  0x55a1bc57eea0 in ???
#1  0x55a1bc57e805 in ???
#2  0x7f441124251f in ???
   at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3  0x55a1bc297f30 in bondedfibre_
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/user/elmt02.f:977
#4  0x55a1bc29fefe in elmt02_
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/user/elmt02.f:214
#5  0x55a1bc04755d in elmlib_
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/program/elmlib.f:66
#6  0x55a1bbf87730 in pcontr_
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/program/pcontr.f:281
#7  0x55a1bbf86d51 in feap
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/main/feap86.f:180
#8  0x55a1bbf86d97 in main
   at /home/peter/Downloads/FEAP86/FEAP86-Fibre-Superelement/main/feap86.f:186
Floating point exception (core dumped)
any idea what that means

Prof. S. Govindjee

  • Administrator
  • FEAP Guru
  • *****
  • Posts: 1160
Re: feap running
« Reply #1 on: May 01, 2023, 08:09:48 AM »
The back trace does tells you that you are looking for some type of floating point error, maybe a division by zero.  Have a look at line 977 in elmt02.f and in the routine bondedfibre.  I would suggest running in a debugger like gdb and putting a breakpoint in elmt02.f at 977 so that you can interrogate the contents of the variables just before the the Floating point exception occurs.