>-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of >David Rothenberger >Sent: Thursday, January 22, 2004 10:32 AM >To: [EMAIL PROTECTED] >Subject: bash, dircolors, setsid and a stackdump > >I've just encountered a very strange problem involving setsid, rxvt, >bash and dircolors. I'm using CVS from Thu Jan 22 07:18:16 PST >2004. > >I have a simple script script.sh: > >---begin script--- >#!/bin/sh >echo foo >sleep 10 >---end script--- > >I have uncommented the dircolors line in the default /etc/profile >and am using the default /etc/DIR_COLORS. > >I start an rxvt window with "rxvt -e bash --login -i". From that >window, I execute "setsid bash script.sh" and get a stackdump from >sleep.exe. > >---begin stackdump--- >Exception: STATUS_ACCESS_VIOLATION at eip=6100256C >eax=616727A4 ebx=00000000 ecx=61670000 edx=435F534C esi=00000EC8 edi=00BE0000 >ebp=0022DA88 esp=0022DA70 program=C:\cygwin\bin\sleep.exe >cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 >Stack trace: >Frame Function Args >0022DA88 6100256C (61670000, 00000002, 0022DAA8, 00000000) >/netrel/src/cygwin-20040122/winsup/cygwin/cygheap.cc:180 [SNIP]
I also see this, with rxvt and zsh. I would dearly love to know how you get those lovely line numbers in the stackdump :) Also I tried setting CYGWIN_DEBUG=sleep, but that never got to attach gdb before the process died. -- Rafael -- 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/
