Skip to contentSkip to conversation

kernel debugging

DISCUSSION UmaMaheswari Devi 4 participants 5 messages Jul 24, 2005 – Jul 25, 2005

lore
Share & tools
lore
#0 lore raw

I am new to kernel hacking and am facing problems in trying to peek at the runtime values of some kernel variables using gdb.

I am issuing the gdb command as follows:
gdb vmlinux /proc/kcore
This displays the message
/proc/kcore: Operation not permitted
before the (gdb) prompt is displayed.
gdb then prints a value of 0 for any valid variable that is requested.

vmlinux appears to be OK, as gdb correctly identifies undefined variables. The problem seems to be with /proc/kcore. This file has a permission of 400. I am using the Red Hat distribution.

Any help is appreciated.

Thanks,
Uma.

#1 lore raw
Quoted 10 lines · UmaMaheswari Devi

I am new to kernel hacking and am facing problems in trying to peek at the runtime values of some kernel variables using gdb.

I am issuing the gdb command as follows:
gdb vmlinux /proc/kcore
This displays the message
/proc/kcore: Operation not permitted
before the (gdb) prompt is displayed.
gdb then prints a value of 0 for any valid variable that is requested.

Quoted 6 lines

vmlinux appears to be OK, as gdb correctly identifies undefined variables. The problem seems to be with /proc/kcore. This file has a permission of 400. I am using the Red Hat distribution.

Any help is appreciated.

If you want to use gdb to debug the kernel you should probably investigate UML (User Mode Linux). Take a look at this link :
http://user-mode-linux.sourceforge.net/debugging.html

Alternatives include kgdb - http://kgdb.sourceforge.net/
and kdb - http://oss.sgi.com/projects/kdb/

You can also find many documents on Linux Kernel debugging aids and techniques via google.

Signature · 3 lines
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
#2 lore raw
Quoted 21 lines · Jesper Juhl
Quoted 10 lines · UmaMaheswari Devi

I am new to kernel hacking and am facing problems in trying to peek at the runtime values of some kernel variables using gdb.

I am issuing the gdb command as follows:
gdb vmlinux /proc/kcore
This displays the message
/proc/kcore: Operation not permitted
before the (gdb) prompt is displayed.
gdb then prints a value of 0 for any valid variable that is requested.

Quoted 6 lines

vmlinux appears to be OK, as gdb correctly identifies undefined variables. The problem seems to be with /proc/kcore. This file has a permission of 400. I am using the Red Hat distribution.

Any help is appreciated.

If you want to use gdb to debug the kernel you should probably investigate UML (User Mode Linux). Take a look at this link :
http://user-mode-linux.sourceforge.net/debugging.html

Quoted 6 lines

Alternatives include kgdb - http://kgdb.sourceforge.net/
and kdb - http://oss.sgi.com/projects/kdb/

You can also find many documents on Linux Kernel debugging aids and techniques via google.

Ohh, and do search the LKML archives, kernel debuggers have been discussed endlessly over the years on the list, so you should be able to find many threads covering that.

Signature · 3 lines
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
#3 lore raw
In reply to UmaMaheswari Devi

I am using Red Hat sources, which has function open_kcore() hardcoded to return -EPERM always.

Changing this function to the way it is defined in the public sources (as shown below) did the trick.

open_kcore(struct inode * inode, struct file * filp) {
return capable(CAP_SYS_RAWIO) ? 0 : -EPERM;
}

I am now able to use gdb to examine kernel symbols.

Uma.

Quoting UmaMaheswari Devi <[email protected]>:

Quoted 1 line

I am new to kernel hacking and am facing problems in tryingstatic int

to peek at the

Quoted 23 lines

runtime values of some kernel variables using gdb.

I am issuing the gdb command as follows:
gdb vmlinux /proc/kcore
This displays the message
/proc/kcore: Operation not permitted
before the (gdb) prompt is displayed.
gdb then prints a value of 0 for any valid variable that is requested.

vmlinux appears to be OK, as gdb correctly identifies undefined variables. The problem seems to be with /proc/kcore. This file has a permission of 400. I am using the Red Hat distribution.

Any help is appreciated. Thanks,
Uma.

-
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/

#4 lore raw
Quoted 5 lines · On Mon, 2005-07-25 at 15:23 -0400, [email protected] wrote:

I am using Red Hat sources, which has function open_kcore() hardcoded to return -EPERM always.

Changing this function to the way it is defined in the public sources (as shown below) did the trick.

All these Red Hat / RHEL threads are completely OT. Please take it to a Red Hat list.

Lee