Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Fri, 26 Jan 2001 00:00:07 -0500
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: minor bug in gcc info files
Message-ID: <20010126000007.C12186@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <3A70C2C0.A22CB4B0@gulftel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3A70C2C0.A22CB4B0@gulftel.com>; from rjob@gulftel.com on Thu, Jan 25, 2001 at 06:20:17PM -0600

On Thu, Jan 25, 2001 at 06:20:17PM -0600, bob olbrich wrote:
>
>Hello,
>
>   I tried to use info to output the node information  for gcc found in \cygwin\usr\info.
>It produced quite a bit of information and then failed:
>
>info: writing node  (gcc.info)  installation
>           "                     "          configuration files
>           o                    o                o
>           o                    o                o
>           o                    o                o
>           "                     "           hex floats
>           "                     "           zero length
> info: cannot find node '(gcc.info)variable length
>           "                     "               macro varargs
>           o                    o                   o
>           o                    o                   o
>           o                    o                   o
>           "                     "                constructors
>0 [main] info 49040715  handle exception   status_acces_violation
>4589 [main]  info 49040715 stackdump: dumping stack_trace to info.exe.stackdump
>segmentation fault (core dumped)
>
>info.exe.stackdump:
>
>Exception: STATUS_ACCESS_VIOLATION at eip=0041059E
>eax=04650634 ebx=0464E930 ecx=FFFFE293 edx=FFFFE293 esi=0464E110 edi=045E3D50
>ebp=025AF87C esp=025AFB34 program=C:\CYGWIN\BIN\INFO.EXE
>cs=0177 ds=017F es=017F fs=1B8F gs=0000 ss=017F
>Stack trace:
>Frame     Function  Args
>025AF87C  0041059E  (00000000, 00000000, 00000000, 00000000)
>025AFB6C  0041059E  (0464E930, 000003E8, FFFFE293, 004050A4)
>025AFBBC  00410246  (045E2C48, 0464DF38, 025AFBEC, 0040F3E4)
>025AFBEC  0040F3C2  (0464DF38, 045E2C48, 0040776C, 610247A1)
>025AFC1C  0040F28E  (045E0758, 045F23F0, 045F23A8, 00415C54)
>025AFC4C  00415759  (045E0758, 045F23F0, 045E60C4, 00000001)
>025AFC7C  00415906  (045E0758, 045F14F0, 045E60C4, 00000001)
>025AFCAC  00415906  (045E0758, 045E2CE0, 045E60C4, 00000001)
>025AFCDC  004159E3  (045E6098, 045E00B0, 00000001, 00407AE1)
>025AFD2C  0040812C  (00000006, 0C5E0C50, 045E0008, FFFFFFFE)
>025AFD88  610038C5  (00000000, 00000000, 4D088DCE, 025AFF68)
>025AFDB8  61003AAD  (00407AD0, 00000000, 839BEE40, 00000000)
>025AFDD8  61003AEC  (00000000, 00000000, FFFFFFFF, 00000001)
>025AFE08  00422DA3  (00407AD0, 025AFC8C, BFFC9490, 025AFF68)
>025AFE38  0040103D  (00000000, 8396BF84, 005A0000, 6F666E49)
>025AFF78  BFF8B537  (839BEDFC, 8396BF84, 00000008, 00000000)
>End of stack trace (more stack frames may be present)
>
>The command that I used after cd'ing to \cygwin\usr\info was:
>
>info -f ./gcc.info -s -o ./gcc.info.txt
>
>My first day with cygwin and I think I found a bug!

You found a problem in info!  Not Cygwin!

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple