From owner-freebsd-ports Tue Aug 21 5: 2:50 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mail.fdma.com (mail.fdma.com [216.241.67.73]) by hub.freebsd.org (Postfix) with ESMTP id BC6F437B40A for ; Tue, 21 Aug 2001 05:02:47 -0700 (PDT) (envelope-from scheidell@mail.fdma.com) Received: (from scheidell@localhost) by mail.fdma.com (8.11.3/8.11.3) id f7LC2Js34833; Tue, 21 Aug 2001 08:02:19 -0400 (EDT) Message-Id: <200108211202.f7LC2Js34833@mail.fdma.com> Subject: Re: anyone else have snort core dump? To: kris@obsecurity.org (Kris Kennaway) Date: Tue, 21 Aug 2001 08:02:19 -0400 (EDT) Cc: freebsd-ports@freebsd.org In-Reply-To: <20010820193712.A7801@xor.obsecurity.org> from "Kris Kennaway" at Aug 20, 2001 07:37:13 PM From: Michael Scheidell X-Loop: scheidell@fdma.com X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > On Mon, Aug 20, 2001 at 03:29:22PM -0400, freebsd-stable@news.fdma.com wrot= > e: > > I have a problem with snort 1.8.1-REL core dumping. > >=20 > > Tried two different systems > >=20 > > one, 133mhz PI, 4.3-REL, stock binaries, dec ethernet card > >=20 > > Two, 850mhz PIII, 4.4-RC2, (not stock) binaries, reltec card > >=20 > > yes, I make sure I took I686_cpu out of make.conf first. > >=20 > > and it core dumps when network is silent or noisy, doesn't matter (seems > > to core dump mostly when silent) > > It's probably a code bug. Unfortunately recent releases of snort > haven't exactly been very stable. I've learned to run it in a > while(1) loop to restart it when it crashes. Ok, here is a different 'twist' on this, has for 12 hours. the 'package' in the ports collection runs fine If I compile it on 4.3-stable (even with NO cpuflags set) it will core dump. Do I need to makeworld on 4.3stable with no cpuflags set? If it runs fine from the package, then it seems to be somerhing in 4.3-stable that would be causing the problem? > No, you should obtain a gdb core traceback and talk to the snort user > support mailing list. It's probably already a known problem. I did report the bug on snort.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message