Just pop open the crashdump and "print *ifp" in the last stack frame before trap.
-a On 11 August 2016 at 16:42, David Wolfskill <da...@catwhisker.org> wrote: > On Thu, Aug 11, 2016 at 04:37:26PM -0700, Adrian Chadd wrote: >> Eep. Is this anotehr case where there's a race and ifp is NULL or the >> ll pointer for ifp is NULL or use-after-free'd? > > I don't know, but it's the only panic of a similar nature I've seen -- > though since on any given day, I'm usually running FreeBSD freshly-built > that morning, "trends" might be a little more difficult to determine. > >> I remember bumping into these here and there because we don't seem to >> have a well defined lifecycle for lladdr access. ;( > > Well, you're quite welcome to grab the crash data & poke around, or tell > me where to look, and I'll do so..... > >> ... >> >> Gory details (both "normal" and gzipped, and including the crash >> >> dump and crashinfo) are in >> >> <http://www.catwhisker.org/~david/FreeBSD/stable_11/2016.08.10/>. >> ... > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > Those who would murder in the name of God or prophet are blasphemous cowards. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"