matthew green <mrg@eterna.com.au> writes:

>    
>    Not to mention that if you get a problem from a piece of the kernel
>    you're not familiar with, finding the call when given the function name
>    is harder than when given the file name.
> 
> if this is a problem -- go directly to pkgsrc/devel/id-utils.
> 
> .mrg.

I don't think anyone is suggestiing the file and number shouldn't also
appear. You want maximal information available when trying to spot
patterns in an assertion errors.