From: "David S. Miller" <davem@redhat.com>
To: latten@austin.ibm.com
Cc: kazunori@miyazawa.org, netdev@oss.sgi.com
Subject: Re: IPSecv6/Neighbor discovery crash
Date: Fri, 22 Aug 2003 15:58:12 -0700 [thread overview]
Message-ID: <20030822155812.06ab718f.davem@redhat.com> (raw)
In-Reply-To: <200308222312.h7MNCAJl019005@faith.austin.ibm.com>
On Fri, 22 Aug 2003 18:12:10 -0500
latten@austin.ibm.com 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 :(
next prev parent reply other threads:[~2003-08-22 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 23:12 IPSecv6/Neighbor discovery crash latten
2003-08-22 22:58 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 1:10 latten
2003-08-22 1:49 latten
2003-08-22 1:46 ` David S. Miller
2003-08-22 5:55 ` Kazunori Miyazawa
2003-08-22 17:50 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030822155812.06ab718f.davem@redhat.com \
--to=davem@redhat.com \
--cc=kazunori@miyazawa.org \
--cc=latten@austin.ibm.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).