On Mar 29 05:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: > Hello List, > > I wonder, if there any special setup was necessary to make coredumps > non-empty. > > When my program crashes it leaves only the following: > > Stack trace: > Frame Function Args > > despite is was built and linked with -g (so should have all the debugging info > intact). I did not modify any shell limits from their stock values, either. > > $ ulimit -a > core file size (blocks, -c) unlimited > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > open files (-n) 256 > pipe size (512 bytes, -p) 8 > stack size (kbytes, -s) 2025 > cpu time (seconds, -t) unlimited > max user processes (-u) 256 > virtual memory (kbytes, -v) unlimited > > Any insight will be greatly appreciated.
If your process crashes with a thoroughly scrambled stack, there's a good chance that Cygwin won't be able to create a stackdump file because it crashes again while producing the stackdump. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpeXe5o65_K6.pgp
Description: PGP signature
