This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
build/1648: version.in corrupted on gdb_6_1-branch
- From: mec dot gnu at mindspring dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 14 May 2004 16:30:12 -0000
- Subject: build/1648: version.in corrupted on gdb_6_1-branch
- Reply-to: mec dot gnu at mindspring dot com
>Number: 1648
>Category: build
>Synopsis: version.in corrupted on gdb_6_1-branch
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Fri May 14 16:38:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: mec.gnu@mindspring.com
>Release: gdb gdb_6_1-branch 2004-05-10 01:52:27 UTC
>Organization:
>Environment:
native i686-pc-linux-gnu
>Description:
The file "version" was corrupted in revision 1.990.2.80 and is now zero-length and staying that way.
The last update on this branch was:
revision 1.990.2.80
date: 2004/05/08 07:00:04; author: gdbadmin; state: Exp; lines: +0 -1
*** empty log message ***
07:00:04 is a strange time for this file to get updated. Usually the file is updated a few seconds after 00:00:00.
This manifests as:
FAIL: gdb.base/selftest.exp: printed version
>How-To-Repeat:
cat version
Or run gdb and observe this:
GNU gdb
Copyright 2004 Free Software Foundation, Inc.
The bug shows up as a lack of version number after "GNU gdb".
>Fix:
This might just auto-fix if someone manually checks in the right contents of "version".
The file got broken about the time that sources.redhat.com was taken down and re-hosted. I don't have an idea how the commit in 1.990.2.80 happened, though.
>Release-Note:
>Audit-Trail:
>Unformatted: