That may be because core dump is turned off (which is default on many Linux distros). If you are using bash, try "ulimit -c" to see if it's the case (it'll return the maximum allowed core size). To turn it on, issue "ulimit -c unlimited" command. For more details, see "man bash" (not "man ulimit" as it is shell command). It only affects the current shell.
HTH, Ed. On Tue, 2009-09-08 at 19:12 -0700, Engin Ozkan wrote: > That is actually a very reasonable request. Sorry for missing that. > However, this bug does not leave any core dumps anywhere I could find, > including in /cores. > > Engin > > On 9/8/09 10:58 AM, Paul Emsley wrote: > > Engin Ozkan wrote: > >> Hi everybody, > >> > >> Using the revision 2283 on 10.5, I am seeing this whenever I am > >> closing the application: > >> > >> /sw/bin/coot: line 5: 19785 Segmentation fault /sw/bin/coot-real > >> "$@" > >> > >> Yep, coot shuts down with a segmentation fault. I haven't tested most > >> functionality and it has not affected my use of coot yet, but I > >> assumed it might help to report it. This seems to be the same bug > >> observed by Christian on a 10.4 machine, because I get the similar > >> Preferences crash. Empty 0-coot.state.scm is also probably due to the > >> crash during exiting. > >> > > > > Dear MacCoot-bug-finders, > > > > It would be very useful (making the difference between a bug being > > probably not fixable to probably fixable) if you could send me the > > core dump analysis of coot. > > > > Coot will leave a core dump in /cores - at least it does for me (look > > for the latest one) > > > > $ gdb /sw/bin/coot-real /cores/cores.xxxx > > where > > > > send me that text output. > > > > Thanks, > > > > Paul > > > > > > --
