Date: Sun, 14 Aug 2016 22:57:49 -0700 From: Adrian Chadd <adrian@freebsd.org> To: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: kernel using gcc-5.3 fails to boot right Message-ID: <CAJ-Vmo=DAgC7x8FECWu_ne-usU4jdCyojFL2HuAJAFj8hmasMA@mail.gmail.com> In-Reply-To: <CAJ-Vmon19GF6N-90avR3%2BPeXkSC=BkNt7Cy2CiVY%2BbwFN5iuMQ@mail.gmail.com> References: <CAJ-VmomVS_fmYo2pvTm85x9tqfRnbcggWW9NLa28BJpfjaFozg@mail.gmail.com> <CAJ-Vmon19GF6N-90avR3%2BPeXkSC=BkNt7Cy2CiVY%2BbwFN5iuMQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, it's something garbage-y showing up in the ipfw init path where it decides to try and malloc a .. very invalidly large chunk. ipfw2 initialized, divert loadable, nat loadable, default to deny, logging disabled CALLING add_sopt_handler: from /usr/home/adrian/work/freebsd/head-embedded/src/sys/modules/ipfw/../../netpfil/ipfw/ip_fw_sockopt.c:3387 ipfw_add_sopt_handler: called; sh=0xc021da50, count=11 ipfw_add_sopt_handler: called; ctl3_hsize=0, sz=11, count=11, (176 bytes) ipfw_add_sopt_handler: called; ctl3_hsize=1142968431, sz=1142968442, count=11, (1107625888 bytes) (That's two loops of the same call to ipfw_add_sopt_handler(), so something in the loop logic isn't right..) -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=DAgC7x8FECWu_ne-usU4jdCyojFL2HuAJAFj8hmasMA>