From owner-freebsd-hackers  Thu Mar 27 21:40:28 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA20991
          for hackers-outgoing; Thu, 27 Mar 1997 21:40:28 -0800 (PST)
Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20984;
          Thu, 27 Mar 1997 21:40:09 -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 AAA05360; Fri, 28 Mar 1997 00:47:00 -0500 (EST)
Message-ID: <333B5B51.41C67EA6@servtech.com>
Date: Fri, 28 Mar 1997 00:46:57 -0500
From: Shawn Carey <smc@servtech.com>
X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-BETA_A i386)
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
CC: dyson@freebsd.org, hackers@freebsd.org
Subject: Re: Anyone else seen this?
References: <199703270427.XAA04344@dyson.iquest.net> <333AA089.41C67EA6@servtech.com> <199703280313.TAA28286@austin.polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

John Polstra wrote:
> 
> In article <333AA089.41C67EA6@servtech.com>,
> Shawn Carey  <smc@servtech.com> wrote:
> > 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.
> 
> Hmm, well I've just been messing around with it, and to me it does seem
> related to GDB.  At least, I can make it happen reliably with GDB,
> but not without GDB.  Mind you, I don't think it's a GDB bug.  It's
> just that GDB writes into the text segments of the executables.
> 

Any chance we have two unrelated but similar problems?  When I run my
executable (linked against shared libs) directly from the shell (GDB not
involved), the timestamp on the file changes every time, though it
appears to run normally.

If I run the same executable under GDB, it runs for 10 seconds at the
most and then GDB kills it before reporting "Process terminated due to
text file modification".  No breakpoints, no nuthin.  Not even a
.gdbinit.

Now, if I link with -static, the exectuable retains its timestamp, even
whe run under GDB, and GDB lets it run peacefully.  I too have seen gdb
touch the files it runs - what I'm talking about here looks to me like
something else.

-Shawn