with my limited knowledge of using gdb without an IDE it got this info:
(gdb) where
#0 0x00007ffff663b418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x00007ffff663d01a in __GI_abort () at abort.c:89
#2 0x00007ffff667d72a in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7ffff6794c7f "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007ffff671e89c in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7ffff6794c10 "buffer overflow detected") at fortify_fail.c:37
#4 0x00007ffff671c8a0 in __GI___chk_fail () at chk_fail.c:28
#5 0x00007ffff671e7e7 in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25
#6 0x000000000041028a in ?? ()
#7 0x0000000000408411 in ?? ()
#8 0x000000000040887f in ?? ()
#9 0x00007ffff79526fa in start_thread (arg=0x7ffff17d1700) at pthread_create.c:333
#10 0x00007ffff670cb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
6,7 and 8 are in the cpuminer code which got terminated unfortunately, someone knows some gdb command to not kill the cpuminer if a buffer overflow is detected so i can check which functions get called?
cheers
cpuminer is trying to create a new thread. This occurs in main() and is very old and
very stable code that hasn't been modified in ages. It's not likely to have a bug.
This could be the compiler or the system (this is the VM right?). The system may be imposing an artificial limitation on resources
that is being exceeded by cpuminer.
I presume you compiled the same way as on other systems so unless there is something else significantly different between them
the obvious conclusion would be that it's because it's a VM.
