Thread (8 messages) 8 messages, 3 authors, 2012-06-26

geting weird semi-random panic on kmalloc

From: NorthPole <hidden>
Date: 2012-06-25 23:22:11

@Mulyadi Santosa

several sources on the net suggested that interactive debuggers on the
kernel are a bad thing so I pushed it down on the todo kernel-skill stack
so I dont yet know how to use qemu's gdb with the kernel

Good news is I found the error (not me the folks at batman's irc channel
did)  the

memcpy(tvlv+sizeof(struct shortTvlv),value,length*sizeof(uint8_t)); needs
to be
memcpy((char *)tvlv+sizeof(struct shortTvlv),value,length*sizeof(uint8_t));

thanks for the assist everyone and if you have any good tutorials on qemu +
kernel +gdb i'll be thankfull


On Fri, Jun 22, 2012 at 7:49 PM, Mulyadi Santosa
[off-list ref]wrote:
Hi...

On Fri, Jun 22, 2012 at 11:27 PM, NorthPole [off-list ref] wrote:
quoted
Hi...

The virtual machine is supposed to run on 128 mb ram and according to the
batman folks its more than enough

How can I force a backtrace?
When it hangs, AFAIK in gdb, press ctrl-c...it will get you back to
gdb prompt ... then type "bt" and Enter.

I assume you use gdb that is hooked into qemu's gdb stub, right?

--
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120626/359d2089/attachment.html 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help