From owner-freebsd-hackers Thu Mar 27 09:47:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00939 for hackers-outgoing; Thu, 27 Mar 1997 09:47:08 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00914 for ; Thu, 27 Mar 1997 09:47:03 -0800 (PST) Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id IAA04746 for ; Thu, 27 Mar 1997 08:25:35 -0800 (PST) Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94]) by boulder.syr.servtech.com (8.8.4/8.8.4) with SMTP id LAA04156; Thu, 27 Mar 1997 11:30:03 -0500 (EST) Message-ID: <333AA089.41C67EA6@servtech.com> Date: Thu, 27 Mar 1997 11:30:01 -0500 From: Shawn Carey X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-BETA_A i386) MIME-Version: 1.0 To: "John S. Dyson" CC: msmith@atrad.adelaide.edu.au, freebsd-hackers@freebsd.org Subject: Re: Anyone else seen this? References: <199703270427.XAA04344@dyson.iquest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson wrote: > > > Shawn Carey stands accused of saying: > > > > > > Now that we are running 2.2-RELEASE, this anomaly appears to be > > > something more serious than I originally thought, as gdb now stops the > > > program with the message "Process killed due to text file modification", > > > and sure enough, the file's date is changing but a diff between an idle > > > copy and the "modified" executable is nil. Furthermore, I have recently > > > discovered that if I link the program with -static, the problem goes > > > away. > > > > This looks very much like a problem that has been reported many times > > before, where one or more pages from a process' text are written back > > to the file. The pages aren't actually changed, but the file's timestamp > > is obviously updated. > > > I have not seen the problem on the 2.2 series recently. However, I seldom > use GDB... Is this a problem that pops up when using GDB (setting breakpoints, > etc.)? If it is, then that will give me a direction to look in. I'll also > look into reproducing the problem this weekend. > The problem is not GDB related, GDB just makes it clear when it happens. When GDB has stopped the program (which is every time so far), I have had no breakpoints or watchpoints set. I'll try running on a readonly filesystem later today. I wish I could send you the source for this program, as it exhibits this behaviour repeatably. Unfortunately, my boss would have kittens if I did this. Please let me know if there's anything you want me to try or look into... -Shawn