> Wouldn't it make more sense to print a stack back trace with function
> names?  That would give much more information.

Just make sure the offsets from the symbol addresses and the
stack address of each frame is reported...

I've actually debugged many a kernel bug from just a traceback
(with all the numbers in hex).

One, previously unmentioned, 'problem' with __FILE__ is that it
is tends to be a rather long string since it is the pathname argument
to cc and may contain a directory name (probably with quite a lot of
../ terms in it).

	David

-- 
David Laight: david@l8s.co.uk