cygwin 1.3.3 announcment -- extra words solicited

[Charles Wilson]

Christopher Faylor wrote:

> On Mon, Sep 03, 2001 at 01:22:41AM -0400, Charles Wilson wrote:
> 
>>Charles Wilson wrote:
>>
>>
>>>cgf wrote:
>>>
>>>>I did a reconfigure and a 'make clean all' without error.
>>>>
>>>*while using a development kernel as your active cgywin1.dll* ?  Or just 
>>>the released 1.3.2 kernel?
>>>
>>
>>cgf wrote:
>>
>>
>>>I always use the latest CVS DLL for everything.  Are you actually doing
>>>a "make install" while running cygwin?  I can see how that could cause
>>>strange problems.
>>>
>>>
>>No, not really.  'make install prefix=$inst/usr exec_prefix=$inst/usr 
>>bindir=$inst/usr/bin libdir=$inst/usr/lib sysconfdir=$inst/etc 
>>includedir=$inst/usr/include tooldir=$inst/usr'
>>
>>But the oops happens during the make, ('make CFLAGS=-O2 tooldir=/usr') 
>>not make install.
>>
>>Thanks for clarifying that you, at least, *are* able to bootstrap (build 
>>a new cygwin while running a devel cygwin).  It's probably just me.
>>
> 
> I'd still like to see exactly where this is dying.  You're saying "make"
> but that doesn't really mean much.  Have you verified that you're dying
> in actual make code as opposed to cygwin1.dll code?


Okay, here's the error message:

make[2]: Leaving directory `/usr/src/cygwin/obj/i686-pc-cygwin/winsup/mingw'
       0 [main] make 1016 open_stackdumpfile: Dumping stack trace to 
make.exe.stackdump
Signal 11
make[1]: *** [bz2lib] Error 139
make[1]: Leaving directory `/usr/src/cygwin/obj/i686-pc-cygwin/winsup'
make: *** [all-target-winsup] Error 2

And the stackdump:

Exception: STATUS_ACCESS_VIOLATION at eip=00410732
eax=00000005 ebx=6141294C ecx=6109A350 edx=610950A0 esi=FFFFFFFF 
edi=00000000
ebp=0022D404 esp=0022D3D4 program=D:\cygwin\bin\make.exe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022D404  00410732  (00000005, 0A01C9C8, 000000C8, 610950A0)
0022D424  61081E8A  (00000005, 0A01C9C8, 000000C8, 0040A5A5)
0022D4D4  0040A5CB  (0A01CB38, 0022D52C, 0040A7DD, 70203B2E)
0022D514  0040A9F9  (0A01CB38, 00000001, 0022D52C, 0042F0B4)
0022D584  0040ACE0  (0022D610, 0022D60C, 00000000, 00404A3D)
0022D624  00404B53  (00000000, 0A01C1F8, FFFFFFFF, 6102BC04)
0022D644  00404FFE  (0A01C1F8, 0A01CB38, 0022D694, 61089BC3)
0022D684  004050D2  (0A01C1F8, 00000000, 0022D6D4, 6107FE5C)
0022D6B4  00405338  (0A01C1F8, 00000000, 00000006, 004264F1)
0022D724  00426617  (0022D7F4, 0A01C1F0, 00000002, 00000000)
0022D834  0041A09D  (0A01BCB8, 0000000A, 00000010, 00000000)
0022D944  00419FD6  (0A01B200, 00000000, 00000058, 00000004)
0022D994  00418912  (00000000, 00000000, 0022FEB4, 00413D37)
0022FEB4  00413D6C  (00000004, 61401DA4, 0A010008, 00000000)
0022FF10  61003E5A  (00000000, 61407DD4, 00000004, 80DE2848)
0022FF40  6100403D  (00412D40, 61407DD4, 81288140, 8046CB60)
End of stack trace (more stack frames may be present)

Decoded (complete version attached).

00410732   job.c:2317 (exec_command)
61081E8A   winsup/cygwin/uinfo.cc:284 (cuserid)
0040A5CB   function.c:1448 (func_shell)
0040A9F9   function.c:1703 (expand_builtin_function)
0040ACE0   function.c:1803 (handle_function)
00404B53   expand.c:253 (variable_expand_string)
00404FFE   expand.c:415 (variable_expand)
004050D2   expand.c:457 (variable_expand_for_file)
00405338   expand.c:535 (allocated_variable_expand_for_file)
00426617   variable.c:888 (try_variable_definition)
0041A09D   read.c:723 (read_makefile)
00419FD6   read.c:702 (read_makefile)
00418912   read.c:234 (read_all_makefiles)
00413D6C   main.c:1503 (main)
61003E5A   winsup/cygwin/dcrt0.cc:863 (dll_crt0_1)
6100403D   winsup/cygwin/dcrt0.cc:929 (_dll_crt0)

Well, I don't think I can really figure out what the problem is unless I 
know what program make is trying to execute in the exec_command() 
function -- but that data doesn't show up in the stackdump.  OTOH, I 
can't just step through the entire build waiting for the crash -- it 
does not appear deterministic.

Should I build dumper.exe and try the JIT functionality?  would that help?

--Chuck