Re: Question regarding the Oops call trace format

[sgrakkyu@xxxxxxxxxx (Oldani Massimiliano)]

On Sat, Mar 06, 2004 at 02:32:20PM -0600, Curran, Dominic wrote:
> 
> Hi
> 
> Below is a Oops of a crash that was reported to the linux1394-devel
> mailing list recently.
> 
> My question is a general one, regarding the format of the Oops call
> trace.
> 
> Taking the first line as an example :
> 
>  [d2235bc0] add_card+0x358/0xa4c [pcilynx]

   format is: function name+offset/total_byte_in_function

> 
> I understand that it references the add_card() function of the [pcilynx]
> driver.
> 
> I assume the first number 0x358 is an offset from the start of the
> add_card() function. Correct ?
> 
> But what does the second number 0xa4c represent ?

    0xa4c is "how long is the function"

>



--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/