On Thu, 3 May 2007 09:01:31 +0200 (MEST) Jan Engelhardt wrote: > > On May 2 2007 15:35, Randy Dunlap wrote: > > > >Add hex_dumper() to lib/hexdump.c and linux/kernel.h. > > Right - we've got the second user already, namely the PANIC/OOPS > code print. (The last line, aka "bytes at EIP" under Windows.) > > Jan 6 14:40:14 deekin kernel: Call Trace: > Jan 6 14:40:14 deekin kernel: [<c02060b3>] is_complete+0x2c3/0x310 > Jan 6 14:40:14 deekin kernel: [<c02037c0>] run+0x30/0x40 > Jan 6 14:40:14 deekin kernel: [<c0125b6d>] worker_thread+0x1bd/0x2b0 > Jan 6 14:40:14 deekin kernel: [<c0203790>] run+0x0/0x40 > Jan 6 14:40:14 deekin kernel: [<c0113b10>] default_wake_function+0x0/0x20 > Jan 6 14:40:14 deekin kernel: [<c0108fd6>] ret_from_fork+0x6/0x20 > Jan 6 14:40:14 deekin kernel: [<c0113b10>] default_wake_function+0x0/0x20 > Jan 6 14:40:14 deekin kernel: [<c01259b0>] worker_thread+0x0/0x2b0 > Jan 6 14:40:14 deekin kernel: [<c0107175>] kernel_thread_helper+0x5/0x10 > Jan 6 14:40:14 deekin kernel: Code: 89 02 8b 41 04 8b 40 3c 8b 53 04 89 42 3c > 8b 41 04
plus intel wireless drivers, 2 MTD/flash drivers, and search kernel tree for hexdump (function name that I wanted to use, but it's already used), hex_dump, dump_hex, dump_mem, etc. Andrew says that he knew of 9 hex dumpers in-tree. :) --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** (sorry about email address change; other address not working for some reason) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
