Re: [ros-kernel] More useful stack traces

[Casper H. <ch...@us...>]

s=F8n, 2002-07-14 kl. 13:53 skrev Casper Hornstrup:
> s=F8n, 2002-07-14 kl. 14:00 skrev David Welch:
> > On Sat, Jul 13, 2002 at 11:27:19PM +0200, Casper Hornstrup wrote:
> > > How?
> > >
> > I think this feature rather falls between two stools: for non-technical=
 users
> > we need a core dump facility which can be automatically decoded offline=
 and
> > emailed to us; developers (who don't have two machines) need a kernel
> > debugger which uses all debugging information and has source code
> > available as well.
>=20
> A core dump facility would be nice, but I think it is complementary to
> the linenumber information in stack traces; not a replacement for it. To
> be able to core dump, the storage driver stack must be loaded so disks
> are accessible. For all crashes before this happens, core dumping is
> useless. Also, I don't always setup a system with a debugger because it
> is difficult and sometimes it helps a lot just knowing the line of code
> where a crash occur.
>=20
> Casper

Also, core dumping is only useful to developers when they have symbol
information. This would mean that either 1) the core dump would contain
the symbols (meaning that non-stripped images need to be used or the
symbols come from the .sym files) or b) core dumps are limited to beeing
generated by official releases so the developer has the symbol
information available. If b) then 6 months is probably too long between
releases. It would be nice if GDB will understand the core dumps.

Casper