| To: | latten@xxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: IPSecv6/Neighbor discovery crash |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Fri, 22 Aug 2003 15:58:12 -0700 |
| Cc: | kazunori@xxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200308222312.h7MNCAJl019005@xxxxxxxxxxxxxxxxxxxx> |
| References: | <200308222312.h7MNCAJl019005@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 22 Aug 2003 18:12:10 -0500 latten@xxxxxxxxxxxxxx wrote: > So I do not know where or what are some of > the values ndisc_output() or ndisc_build_ll_addr() are using. > Nothing gets written to my log file when I do the ping6. ... > > > EIP is at ndisc_build_ll_hdr+0x17/0x1e0 Why not save yourself all that debugging effort and just use gdb on the kernel image and: (gdb) x/10i ndisc_build_ll_hdr+0x17 then match that assembler up with the output of: bash$ make net/ipv6/ndisc.s I'm flabbergasted that someone would resort to printk()'s to figure out the precise location of this OOPS when the OOPS says exactly the location :( |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPSecv6/Neighbor discovery crash, latten |
|---|---|
| Next by Date: | Re: IPSecv6/Neighbor discovery crash, latten |
| Previous by Thread: | Re: IPSecv6/Neighbor discovery crash, latten |
| Next by Thread: | Re: IPSecv6/Neighbor discovery crash, latten |
| Indexes: | [Date] [Thread] [Top] [All Lists] |