Re: Pointer to info on decoding oops messages

["Randy.Dunlap" <rddunlap@osdl.org>]

On Thu, 27 Nov 2003 09:54:05 +0800 (WST) Ian Kent <raven@themaw.net> wrote:

| On Wed, 26 Nov 2003, Ian Kent wrote:
| 
| >
| > The subject says it all.
| >
| 
| Once upon a time, in a galaxy far away I could get an assembly listing
| with original source lines interspersed. This would allow me to quickly
| identify the address (source line) causing a problem from stack dumps.
| 
| Anyone know how this can be acheived with gcc and the kernel source.

[See MOTD, below.]

In 2.6.x, you can do this:

  make drivers/usb/core/usb.lst

This doesn't work in 2.4 (at least not in 2.4.22, where I
tested it).  You can always use objdump to list an object file,
but it doesn't provide mixed source/object lines.

There was a question similar to this on the gcc mailing list a few
weeks ago.  One answer posted was this (from Jim Wilson):

  If you are using GNU as, then see the GNU as docs for the -a option 
  which produces listings file.  Try for instance
	gcc -O -g -Wa,-ahls file.c

so maybe you change some CFLAGS or AFLAGS etc. in Makefile and have
'as' generate a listing for you.

--
~Randy
MOTD:  Always include version info.