From: http://kerneltrap.org/sup/3648/oops-tracing.txt
Example:
Oops message:
Pid: 5802, comm:      testMuctpiReado
EIP: 0060:[<f8b8564e>] CPU: 0
EIP is at vme_rcc_ioctl+0x171e/0x31dd [vme_rcc]
  EFLAGS: 00000286    Tainted: P       (2.6.18-164.11.1.el5 #1)
EAX: 00000000 EBX: c52c3e00 ECX: 00000000 EDX: 00000200
ESI: 0000000a EDI: 00000118 EBP: 000003e8 DS: 007b ES: 007b
CR0: 8005003b CR2: b2157000 CR3: 0a0ac000 CR4: 000006d0
  [<c04c6a2f>] inode_has_perm+0x54/0x5c
.....

Commands:

> cd /home-users/joos/DAQ/DataFlow/ROSRCDdrivers/i686-slc4-gcc34-dbg.
> gdb vme_rcc-2.6.18-194.el5.ko
(gdb) list *vme_rcc_ioctl+0x171e

0x464e is in vme_rcc_ioctl (/home-users/joos/DAQ/DataFlow/ROSRCDdrivers/src/vme_rcc.c:1347).

-- MarkusJoos - 12-Apr-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-04-12 - MarkusJoos
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback