From owner-shore-bugs@cs.wisc.edu Fri Aug 23 16:56:24 2002 Received: (from majordom@localhost) by jeeves.cs.wisc.edu (8.9.2/8.9.2) id QAA25605; Fri, 23 Aug 2002 16:56:24 -0500 (CDT) X-Authentication-Warning: jeeves.cs.wisc.edu: majordom set sender to owner-shore-bugs@cs.wisc.edu using -f Received: from lucy.cs.wisc.edu (lucy.cs.wisc.edu [128.105.6.15]) by jeeves.cs.wisc.edu (8.9.2/8.9.2) with ESMTP id QAA25597; Fri, 23 Aug 2002 16:56:24 -0500 (CDT) Received: from newman.cs.purdue.edu (IDENT:0@newman.cs.purdue.edu [128.10.2.6]) by lucy.cs.wisc.edu (8.11.3/8.11.3) with ESMTP id g7NLuNb31880; Fri, 23 Aug 2002 16:56:23 -0500 Received: from jabberwock.cs.purdue.edu (jabberwock.cs.purdue.edu [128.211.1.82]) by newman.cs.purdue.edu (8.11.6/8.11.6/PURDUE_CS-2.0) with ESMTP id g7NLuMn09042; Fri, 23 Aug 2002 16:56:22 -0500 (EST) Received: from localhost (welc@localhost) by jabberwock.cs.purdue.edu (8.11.6/8.11.6/PURDUE_CS-2.0) with ESMTP id g7NLuLs15523; Fri, 23 Aug 2002 16:56:22 -0500 Date: Fri, 23 Aug 2002 16:56:21 -0500 (EST) From: Adam Welc To: shore-bugs@cs.wisc.edu cc: shore-users@cs.wisc.edu Subject: bug in the "Interim Snapshot 2 -- February 2002" Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-746565119-539255535-1030139781=:15474" X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-shore-bugs@cs.wisc.edu Precedence: list This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---746565119-539255535-1030139781=:15474 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I have recently donwloaded the newest snapshot and I noticed, that one of the bufs I reported over a year ago is stil not fixed. For those interested, I am sending a diff between original (from the snapshot) version of the file and the fixed one. This error occurs at multiple chain operations. The bug is located in sm.cpp file. The local variable stats is NOT initialized to 0 (it's value is unspecified), then it gets stored by give_stats() (within _chain_xct()). Potentially, later on, it may get obtained by steel_stats() (also in _chain_xct()) and deallocated (using delete operator on a pointer with undefined value will yield unpredictable results). Best regards Adam Welc P.S. Does anybody know when can we expect a release that would fix a with assertion failure in diskrw process (mentioned in the README for the current snapshot, but not yet fixed). It is apparently not that rare, since I stumbled upon it... -- Adam Welc Computer Science Building, room 274 West Lafayette, IN 47906 Telephone number (work): (765) 4947836 http://www.cs.purdue.edu/homes/welc ---746565119-539255535-1030139781=:15474 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=diff Content-ID: Content-Description: Content-Disposition: attachment; filename=diff Content-Transfer-Encoding: BASE64 MTQxNWMxNDE1DQo8ICAgICBzbV9zdGF0c19pbmZvX3QqICBzdGF0czsNCi0t LQ0KPiAgICAgc21fc3RhdHNfaW5mb190KiAgc3RhdHM9MDsNCg== ---746565119-539255535-1030139781=:15474--