Re: why can't i use gdb to dump module variables anymore?

["Robert P. J. Day" <rpjday@crashcourse.ca>]

On Sun, 8 Aug 2010, Jon Masters wrote:

>
> On Jul 8, 2010, at 7:51 AM, Robert P. J. Day wrote:
> >
> > (gdb) p rpjday_2
> > Cannot access memory at address 0xffffffffa007c0b4
> > (gdb) p rpjday_3
> > Cannot access memory at address 0xffffffffa007c0b8
>
> Did you ever get a reply to this one? Were you trying to do this
> locally, by loading a kernel core or using kgdb?

  never figured out what was happening here, used to work just fine
for simple gdb debugging of the kernel; nowadays (at least on ubuntu),
not so much.  anyway, i'm in bahstahn for linuxcon, staying at the
onyx hotel for first 3 days.  my girlfriend is doing a bofs session:

http://events.linuxfoundation.org/linuxcon2010/mckinnon

  anyway, regarding gdb, this was based on a column i wrote last
year:

http://www.linux.com/learn/linux-training/33991-the-kernel-newbie-corner-kernel-and-module-debugging-with-gdb

where it worked just fine -- it's the technique described in LDD3.
but now, on ubuntu 10.04, weirdness.  i haven't looked at it closely
again for a while, but if you have any ideas, i'm open to suggestions.
maybe some odd security/selinux/??? setting?

rday


-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Top-notch, inexpensive online Linux/OSS/kernel courses
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================