On Sun, 21 Nov 2004 11:42:02 -0800 (PST), cranium2003 <cranium2003@xxxxxxxxx> wrote: > > --- Nish Aravamudan <nish.aravamudan@xxxxxxxxx> wrote: > Hello Nish, > > > > > On Sun, 21 Nov 2004 17:15:12 +0100 (MET), Jan > > Engelhardt > > <jengelh@xxxxxxxxxxxxxxx> wrote: > > > >hello, > > > > In ip_output.c file ip_fragmet function > > when > > > >create a new fragmented packet given to > > output(skb) > > > >function. i want to know which function are > > actually > > > >called by output(skb)? > > > > > > use stack_dump() (or was it dump_stack()?) > > > > dump_stack(), if you want to dump the current > > process' stack context. > > > > -Nish > > > > can you please tell me how can i use dump_stack() > method? so using dump_stack i will come to know which > function will be called by output(skb) right? But > where i get dump_stack()??? Last time i used it, I didn't need to do a darn thing. I believe it's part of the traps code, so you can just call dump_stack(). dump_stack() will throw out the trace of the current task's stack at the point when it is called. See what happens when you place it in different places. Another option, if you ever have a hanging sytem is Alt-SysRq-T (presuming you have the magic option enabled and you are able to scrollback still), which pretty much calls dump_stack() for all available processes. -Nish -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
