[netflow-tools] Python flowd module causing SIGBUS on OpenBSD/sparc64

Damien Miller djm at mindrot.org
Mon Sep 17 16:20:17 EST 2007

On Thu, 6 Sep 2007, Ben Lovett wrote:

> On Sep 3, 2007, at 3:49 AM, Damien Miller wrote:
> > It looks like something is hosing memory, but the crash doesn't seem
> > to be proximal to the actual corruption. Turning on those malloc  
> > options
> > might expose the corruption closer to where it occurs.
> Rebuilt python with debugging symbols for good measure.
> It doesn't make much sense to me that it would be crashing in a  
> return.. But I suppose that is just another indication that something  
> is going terribly wrong.

Yes, it looks like something has hosed the stack, or gdb is misbehaving.
Either way, it doesn't give much to go on.

> selenium:~ % env MALLOC_OPTIONS=AFGJP python2.4
> Python 2.4.4 (#1, Sep  3 2007, 13:24:30)
> [GCC 3.3.5 (propolice)] on openbsd4
> Type "help", "copyright", "credits" or "license" for more information.
>  >>> import flowd
>  >>> flows = flowd.FlowLog("flowd-blah.log", "rb")
>  >>> for flow in flows:
> ...     print flow.format()

Could you try printing out the flow fields manually and seeing if you can
elicit a crash?


More information about the netflow-tools mailing list