Segmentation Fault for large images

[Bovornpratch]

Hi,

I am using sextractor for some large mosaic images (a few MegaPx^2 size) and sometimes during the analysis phase (before writing that catalog), sextractor crashes with a segmentation fault.

I found that increasing the MEMORY BUFSIZE, MEMORY OBJSTACK, and MEMORY PIXSTACK seems to resolve the issue in some cases. However, I am curious what is the actual reason in which causes this crash and how to avoid it.

[mingyangzhuang]

Hi @Bovornpratch

I also ran into this issue with a large mosaic (~100k x 100k pix^2). Could you share with me your MEMORY BUFSIZE, MEMORY OBJSTACK, and MEMORY PIXSTACK?

Many thanks!

Hi,

I am using sextractor for some large mosaic images (a few MegaPx^2 size) and sometimes during the analysis phase (before writing that catalog), sextractor crashes with a segmentation fault.

I found that increasing the MEMORY BUFSIZE, MEMORY OBJSTACK, and MEMORY PIXSTACK seems to resolve the issue in some cases. However, I am curious what is the actual reason in which causes this crash and how to avoid it.

[rmathar]

To help debugging, you could set AM_CFLAGS in Makefile.am to -g -O0 -fsanitize=address -fsanitize=null -fsanitize=bounds-strict -fsanitize=alignment -fsanitize=return -fsanitize=object-size -fsanitize=vptr -fsanitize=integer-divide-by-zero -fstack-protector-all -fno-omit-frame-pointer -fsanitize=undefined -fsanitize-address-use-after-scope, recompile, run, and tell us what the pointer checkers tell.