Adding full segment data is an important improvement, but that misses some obvious data that you want. Section information (not in a loadable segment) is also important. The new coreadm allows the user to add the "ctf" and "symtab" non-loadable sections, but not stabs or dwarf information. This is a pretty serious omission for observability, since there are a fair number of customers who want source-level stack dumps and debugging, as well as C++ support.
--chris Adam Leventhal wrote: > On Sun, Oct 16, 2005 at 10:46:20PM -0700, Rod Evans wrote: > >>I (and the debugging folks) have come across a number of applications >>who try and print stack traces on a fatal error, and then prevent any >>core from being produced at all. Historic issues like the core being >>too large to leave in the cwd, or the core not being debuggable in >>different system environments, have now changed. coreadm(1) exists, and >>core files can contain every segment of the original image. > > > With coreadm(1M, you can, indeed, include data from whatever segments > you want in the core file -- including the read-only data will get you > the .dynsym section. You can also include the .symtab section, but, > unlike text, is not included by default. > > Adam >
