If you're out of space on your device perhaps try to write somewhere else. You can get data about a running process via gdb but that only helps if the process is hung and you're willing to get the info that way (vs. a core generated from a crash). Other things from core notes:
Enabling Application Core Dumps The location and naming of application core dumps are based on the following sysctl options: kernel.core_pattern=[/path/to/cores/]core If the path is not specified the application's CWD is used (commonly /) kernel.core_uses_pid=0 - Causes the pid of the process to be appended to the name of the core So, specify somewhere you do have room to write the core and then try to generate the core. Hope that helps, AB On Mon, Nov 29, 2010 at 07:53, David Wilcox <[email protected]> wrote: > Hi, > > I have been running up against the following error when trying to generate > core dumps from a particular process: <code>warning: Failed to write > corefile contents (No space left on device).</code> > http://webcache.googleusercontent.com/search?q=cache:tLciVD0zeVUJ:cygwin.ru/ml/gdb/2009-09/msg00319.html+warning:+Failed+to+write+corefile+contents+%28No+space+left+on+device%29.&cd=2&hl=en&ct=clnk&gl=us&client=ubuntu > makes be believe that it is due to the fact that my process uses a lot of > RAM. I checked, and sure enough, my process was using a large percent of the > system RAM. Is there any way to generate a core backtrace from large > processes? I'm looking for a low-RAM alternative to the conventional methods > of generating core backtraces. > > David > > -------------------- > BYU Unix Users Group > http://uug.byu.edu/ > > The opinions expressed in this message are the responsibility of their > author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. > ___________________________________________________________________ > List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list > -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
