This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: cygwin 1.3.3 announcment -- extra words solicited
Hi!
Tuesday, 04 September, 2001 Charles Wilson cwilson@ece.gatech.edu wrote:
CW> Decoded (complete version attached).
CW> 00410732 job.c:2317 (exec_command)
CW> 61081E8A winsup/cygwin/uinfo.cc:284 (cuserid)
CW> 0040A5CB function.c:1448 (func_shell)
CW> 0040A9F9 function.c:1703 (expand_builtin_function)
CW> 0040ACE0 function.c:1803 (handle_function)
CW> 00404B53 expand.c:253 (variable_expand_string)
CW> 00404FFE expand.c:415 (variable_expand)
CW> 004050D2 expand.c:457 (variable_expand_for_file)
CW> 00405338 expand.c:535 (allocated_variable_expand_for_file)
CW> 00426617 variable.c:888 (try_variable_definition)
CW> 0041A09D read.c:723 (read_makefile)
CW> 00419FD6 read.c:702 (read_makefile)
CW> 00418912 read.c:234 (read_all_makefiles)
CW> 00413D6C main.c:1503 (main)
CW> 61003E5A winsup/cygwin/dcrt0.cc:863 (dll_crt0_1)
CW> 6100403D winsup/cygwin/dcrt0.cc:929 (_dll_crt0)
CW> Well, I don't think I can really figure out what the problem is unless I
CW> know what program make is trying to execute in the exec_command()
CW> function -- but that data doesn't show up in the stackdump. OTOH, I
CW> can't just step through the entire build waiting for the crash -- it
CW> does not appear deterministic.
CW> Should I build dumper.exe and try the JIT functionality? would that help?
it would be enough (and probably easier) to use JIT debugging with
gdb. adding 'error_start=x:\path\to\gdb\gdb.exe' to CYGWIN environment
variable should do.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19