On Thu, 8 Jul 2010, Prabhunath G wrote:
>
> Hi Robert,
>
> Can you please share the writeup that you have written to use gdb to
> debug a
> running kernel for
> a 32-bit system.
>
> Thanks,
> Prabhu
and this is where it gets awkward since, as i've mentioned before,
i'm currentl
On Thu, 8 Jul 2010, Mulyadi Santosa wrote:
> On Thu, Jul 8, 2010 at 02:13, Robert P. J. Day wrote:
> > in fact, that's exactly the right value based on this snippet from
> > init/main.c:
> >
> > unsigned long loops_per_jiffy = (1<<12);
> >
> > which is, of course, 4096.
>
> Thanks for sharing..
On Thu, Jul 8, 2010 at 02:13, Robert P. J. Day wrote:
> in fact, that's exactly the right value based on this snippet from
> init/main.c:
>
> unsigned long loops_per_jiffy = (1<<12);
>
> which is, of course, 4096.
Thanks for sharingso it's fixed in 64 bit environment...I assumen
it's x64..
ok, part of the mystery is solved and i'm just being an idiot:
On Wed, 7 Jul 2010, Robert P. J. Day wrote:
> and this is also weird:
>
> (gdb) p loops_per_jiffy
> $16 = 4096
>
> huh? that value is way too low for this system. on my old 32-bit
> system, that value would be around 2 million
On Thu, 8 Jul 2010, Mulyadi Santosa wrote:
> On Thu, Jul 8, 2010 at 01:19, Robert P. J. Day wrote:
>
> > however, since this *is* a 64-bit system, i apparently have no such
> > symbol, i would just use:
> >
> > (gdb) p __jiffies
> > $12 = 4294937296
> > (gdb) p __jiffies
> > $13 = 4294937296
> >
On Thu, Jul 8, 2010 at 01:19, Robert P. J. Day wrote:
> however, since this *is* a 64-bit system, i apparently have no such
> symbol, i would just use:
>
> (gdb) p __jiffies
> $12 = 4294937296
> (gdb) p __jiffies
> $13 = 4294937296
> (gdb) p __jiffies
> $14 = 4294937296
two things I would check
currently, i'm working on a short writeup showing how to use gdb to
debug a running kernel and, when i first wrote this a while back, it
was for a 32-bit system and things worked just fine.
in short, i fired up gdb using the standard kernel-oriented
invocation with:
$ sudo gdb /tmp/vmlinux
