Re: Cygwin: texi2dvi stumbles over texinfo.tex

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Fri, May 26, 2006 at 06:46:21AM +0200, Ralf Wildenhues wrote:
>$ cat texindex.exe.stackdump 
>Exception: STATUS_ACCESS_VIOLATION at eip=6105440C
>
>eax=0000004A ebx=00000003 ecx=00000013 edx=02B9E8A9 esi=00405457 edi=0040544D
>
>ebp=0022EE08 esp=0022ED60 program=C:\cygwin\bin\texindex.exe, pid 296, thread main
>
>cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
>
>Stack trace:
>
>Frame     Function  Args
>
>0022EE08  6105440C  (00460210, 00000000, 0022EEC8, 6108DD7F)
>
>0022EE18  61054685  (0040544D, 6115E684, 00000000, 00403229)
>
>0022EEC8  6108DD7F  (00000005, 6115E684, 00460090, 77DADB0D)
>
>0022EF78  61005BC8  (0022EFD0, 00000000, 00000002, 00000000)
>
>0022FF88  61005EB3  (00000000, 00000000, 00000000, 00000000)

That's apparently a call to mktemp, although I can't tell what's causing
the problem.

Setting the CYGWIN environment variable to error_start:gdb might help
with finding what the argument to mktemp is.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/