From nobody  Mon Sep  1 03:15:34 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA18184;
          Mon, 1 Sep 1997 03:15:34 -0700 (PDT)
Message-Id: <199709011015.DAA18184@hub.freebsd.org>
Date: Mon, 1 Sep 1997 03:15:34 -0700 (PDT)
From: switzel@uni-goettingen.de
To: freebsd-gnats-submit@freebsd.org
Subject: segmentation fault in vfprintf
X-Send-Pr-Version: www-1.0

>Number:         4445
>Category:       bin
>Synopsis:       segmentation fault in vfprintf
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep  1 03:20:01 PDT 1997
>Closed-Date:    Thu Oct 2 18:29:09 MEST 1997
>Last-Modified:  Thu Oct  2 18:29:43 MEST 1997
>Originator:     Stefan Witzel
>Release:        2.2.2-RELEASE
>Organization:
Universitaet Goettingen
>Environment:
FreeBSD thrake.zvw.uni-goettingen.de 2.2.2-RELEASE 2.2.2-RELEASE #0
>Description:
Running ipmon -F from Darren Reed's ipfilter V3.2beta3  causes a core dump:

   8000 bytes flushed from log buffer
   [....] pid 191 (ipmon) uid 0: exited on signal 11 (core dumped)
   Segmentation fault (core dumped)

Recompiling  ipmon with the -g option and running it under gdb gives 

   0x8061e3a in vfprintf ()

when processing line 602 in ipmon.c:

   fprintf(log, "%d bytes flushed from log buffer", flushed);

If I replace line 602 by 

   printf("%d\n", flushed);

there is any problem.

Some more informations:

   whatis flushed: type = int
   print flushed: $1 = 8160

   Processor: AMD K5-P133
 


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: switzel@uni-goettingen.de
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/4445: segmentation fault in vfprintf
Date: Sun, 7 Sep 1997 09:33:40 +0200

 As switzel@uni-goettingen.de wrote:
 
 > when processing line 602 in ipmon.c:
 > 
 >    fprintf(log, "%d bytes flushed from log buffer", flushed);
 > 
 > If I replace line 602 by 
 > 
 >    printf("%d\n", flushed);
 > 
 > there is any problem.
 
 Which suggests that there's something wrong with `log'.
 
 Can you reproduce and track this further (e.g. by linking a private
 copy of the printf stuff so it's compiled with -g, too)?
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Thu Oct 2 18:29:09 MEST 1997 
State-Changed-Why:  

Cancelled by originator's requeust. 
>Unformatted:
