Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Dear all,
I was trying to run a simulation. I am getting error like
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x146f990afd11 in ???
#1 0x146f990aeee5 in ???
#2 0x146f95fdf08f in ???
at /build/glibc-wuryBv/glibc-2.31/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
#3 0x561f8215e530 in ???
#4 0x561f819cc7db in ???
#5 0x561f816353e5 in ???
#6 0x561f80ec5d7a in ???
#7 0x561f808ff7d8 in ???
#8 0x561f80794bf3 in ???
#9 0x561f7f7d60be in ???
#10 0x561f7f75cfd7 in ???
#11 0x561f7f75ca0e in ???
#12 0x146f95fc0082 in __libc_start_main
at ../csu/libc-start.c:308
#13 0x561f7f75ca4d in ???
#14 0xffffffffffffffff in ???
Even I have tried all the possibilities from Choosing an Appropriate Number of Processors and What is the most common reason for a segmentation fault?. I have even tried running it with multiple processors. I was not able to resolve the problem. I have attached my files here for reference.
 

Attachments

  • namelist.input
    3 KB · Views: 5
  • rsl.error.0000
    3.8 KB · Views: 5
  • rsl.out.0000
    3.2 KB · Views: 1
Hi,
Given the size of your domain, you should need to use multiple processors. I know you said you did this, but I'd like to see the output from a simulation you tried like that. Can you try using something like 64 processors and see what happens. Assuming it will still fail, will you package all of the rsl* files into a single *.tar file and attach that? Thanks.
 
Top