Re: tty-related oops in latest kernel(s)?

On 5/28/07, Pekka Enberg <[email protected]> wrote:

Can we have your .config please? Also, could you work out the file and
line number of vt_ioctl+0xda8/0x1482 like this:

gdb vmlinux
(gdb) l *0xc021e50e

Btw, this only works if you have CONFIG_DEBUG_INFO set. In case it
wasn't, please do:

- Enable CONFIG_DEBUG_INFO
- make vmlinux
- gdb vmlinux
(gdb) p vt_ioctl
(gdb) l *(0x<address of vt_ioctl> + 0xda8)
-
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/

---

• References:
  • tty-related oops in latest kernel(s)?
    • From: Tero Roponen <[email protected]>
  • Re: tty-related oops in latest kernel(s)?
    • From: "Pekka Enberg" <[email protected]>

• Prev by Date: [PATCH] Documentation: How to use GDB to decode OOPSes
• Next by Date: [PATCH] kernel/sched.c: use list_for_each_entry_safe() in __wake_up_common()
• Previous by thread: Re: tty-related oops in latest kernel(s)?
• Next by thread: Re: tty-related oops in latest kernel(s)?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]