| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <b6c5339f0904050743k799104f1x443edb69a00fdb64@mail.gmail.com> Date: Sun, 5 Apr 2009 10:43:20 -0400 From: Bob Copeland <me@...copeland.com> To: Peter Hallberg <hallberg68@...mail.com> Cc: Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: Intepreting an oops On Sun, Apr 5, 2009 at 9:01 AM, Avi Kivity <avi@...hat.com> wrote: > Peter Hallberg wrote: >> >> How does one translate the offset in the function to a line number in the >> source code? >> [ 218.418473] Call Trace: >> [ 218.418484] [] :nnpfs:nnpfs_writepage+0xab/0x230 >> > > You can use 'objdump -Sr nnpfs.ko' and look for the address of > nnpfs_writepage, plus 0xab. I use the above sometimes, also you can do: gdb nnpfs.ko gdb> l *(nnpfs_writepage+0xab) Documentation/oops-tracing.txt has some helpful tips. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists