Memory Allocation Table question ??

[William Case]

Hi David;

On Thu, 2008-02-21 at 00:50 -0500, David C. Chipman wrote:
> On Wed, 20 Feb 2008 11:41:33 -0500
> William Case <billlinux at rogers.com> wrote:
> 
> > Hi;
> > 
> > Today Ray Pittigher in his posting "Subject:Is this a Kernel Problem?
> > (sh: page allocation failure. order:4, mode:0xd0)" included a table of
> > memory allocations:
> >         "sh: page allocation failure. order:4, mode:0xd0
> >           [<c0144410>] __alloc_pages+0x294/0x2a6
> >           [<c014443a>] __get_free_pages+0x18/0x24
> >           [<c0146f60>] kmem_getpages+0x1c/0xbb
> >           [<c0147aae>] cache_grow+0xab/0x138
> >           [<c0147ca0>] cache_alloc_refill+0x165/0x19d
> >           [<c0148074>] __kmalloc+0x76/0x88
> >           [<c013dff9>] audit_bprm+0x52/0x10a
> >           [<c014b953>] kunmap_high+0x63/0x80
> >           [<c0163aed>] copy_strings+0x22b/0x235
> >           [<c0164b66>] search_binary_handler+0x32/0x22a
> >           [<c0164ecb>] do_execve+0x16d/0x1fd
> >           [<c01049d5>] sys_execve+0x2b/0x8a
> >           [<c02d5ee3>] syscall_call+0x7/0xb
> >          Mem-info: etc ..."
> > 
> > I have been looking for such a table for my memory allocations (just
> > for a look-see).  What command or utility can I use to get such a
> > table?
> > 
> > I would like to actually see (just for curiosity and understanding of
> > how memory works) user space and kernel space allocations.  I have
> > several manuals that explain the use of memory, so I don't need more
> > of that type of reading.  I just want one look at the "real thing" on
> > my own computer.
> > 
> > Can anyone make some suggestions?
> > 
> 	Hi William, 
> 
> 		I must tell you, hat you posted is called a "stack
> trace", and it's formatting is that of the kernel, when it dies on ya,
> not a print out of a "Memory Allocation Table". It let's you know where
> there is a bug in the kernel. Did it come up while you were tryign to
> start a program? That's certainly what it looks like (the last four
> lines, before "Mem-info etc..."). 
No, it didn't come up for me.  It was the stack trace that Ray Pittigher
included in his posting "Subject:Is this a Kernel Problem?".  I didn't
know what to call it, but it had the type of information I have been
looking for. i.e. storage location; name of process, variable or
whatever; size etc.
 
> How ever, you might be able to get
> the info you're looking for from twiddling with the "top" command (some
> things you seem to be asking about are not a part of the top command's
> default display, but I imagine it can be configured to do so). 

I have tried top and/or ps; I was hoping I could get a screen print of
my current memory headings and addresses so that I could say to myself
(in a visual way as well as by calculation based on textual descriptions
in manuals) "Ah here is where the BIOS has been moved to, and here is
where the kernel space starts and ends and here is the user space.
Perhaps, here is where the DMA and/or NIC data is stored (or piped or
socketed) and here is the addresses to devices and drivers."  I
understand all this is somewhat dynamic -- but visual cues do help
understanding.

-- 
Regards Bill