Date: Mon, 9 Jun 1997 20:56:35 -0700 (PDT) From: "Jin Guojun[ITG]" <jin@iss-p1.lbl.gov> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/3827: fopen/freopen fails on some binary files. Message-ID: <199706100356.UAA20118@iss-p1.lbl.gov> Resent-Message-ID: <199706100400.VAA06490@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3827 >Category: kern >Synopsis: fopen/freopen fails on some binary files. >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 9 21:00:00 PDT 1997 >Last-Modified: >Originator: Jin Guojun[ITG] >Organization: >Release: FreeBSD 3.0-970527-SNAP i386 >Environment: FreeBSD 3.0-970527-SNAP >Description: freopen() fails on about 50% binary files. It causes application handing. The programs are used for reading images and processing for enhancement. The first part reads the header (Text). When read/fread hang, the top show that it uses all available CPU. If SMP is enabled, this hanging process will take about at least one minute to be killed. In non-SMP kernel, it can be killed immediately. In gdb, after freopen(), do "p ftell(fp)" will get bad memory error. open() has the same problem. The same application using "<" works OK. >How-To-Repeat: No regular pattern for such failure. Normally, for same reading code, keep adding more code after it (such as more subroutines), the reading code will hang at reading same binary file. >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706100356.UAA20118>