bash, dircolors, setsid and a stackdump

Rafael Kitover
Fri Jan 23 02:07:00 GMT 2004

>-----Original Message-----
>From: [] On Behalf Of
>David Rothenberger
>Sent: Thursday, January 22, 2004 10:32 AM
>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
>I have a simple script
>---begin script---
>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" and get a stackdump from
>---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)

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.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list