On Mon, 04 Jan 2010 08:07:45 +0900 Tejun Heo <tj@xxxxxxxxxx> wrote: > On 01/04/2010 08:01 AM, Arjan van de Ven wrote: > > On Mon, 04 Jan 2010 07:49:56 +0900 > > Tejun Heo <tj@xxxxxxxxxx> wrote: > >> > >> If implementing parsing of oops message in C is too awkward > >> (unsurprising at all), maybe implementing a converter in perl or > >> python is the easiest way so that it takes the oops message and > >> puts out well formatted input for the s2c program? > > > > you mean like scripts/markup_oops.pl ? > > Whichever one works but s2c wouldn't require symbol decoding. Maybe > we can simply add an option to tell it to just parse the oops and > output it in machine friendly format. Oh, also, the patch does add > new information the module load addresses. We should be able to add > those to the oops message in a compact form. actually one does not need those; you know the start address of the function already from the current oops output, and since you know the address of the function within the module as well, you know the start address of the module. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org
