This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.5.25: Random segfaults in unix tools
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 27 May 2008 10:05:38 -0400
- Subject: Re: 1.5.25: Random segfaults in unix tools
- References: <BLU116-W26BA00024BFA1EA385E65FEFBD0@phx.gbl>
- Reply-to: cygwin at cygwin dot com
On Tue, May 27, 2008 at 02:36:18PM +0100, Jamie Cole wrote:
>
>
>I'm using Cygwin to provide the UNIX utilities such as sed, awk, cut etc. to a Windows server. This process works correctly on our dev server, but when using the same shells and Cygwin install on our prod box these tools randomly segfault.
>
>The processes will work a number of times (seemingly random), but after a few runs will invariably begin to segfault as shown below, the only solution is to bounce the box and we get a few more runs before futher segfaults.
>
>
>Exception: STATUS_ACCESS_VIOLATION at eip=8B909090
>eax=00000000 ebx=61168990 ecx=00000007 edx=00000000 esi=611689B8 edi=0022C900
>ebp=0022C858 esp=0022C850 program=C:\cygwin\bin\cut.exe, pid 1620, thread main
>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
>Stack trace:
>Frame Function Args
>0022C858 8B909090 (611689B8, 61168990, 10000000, 61168990)
>0022C888 61084107 (0022C900, 00000001, 00000001, 61168990)
>0022C8B8 6108447D (00000000, 00000000, 6110941C, 7D61C92D)
>0022CCE8 61096FB4 (00000000, 00000400, 00000000, 00000000)
>0022CD98 6100552E (00000000, 0022CDD0, 61005450, 0022CDD0)
>61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48)
>19 [main] cut 1620 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
>
>What is causing the segfaults and how can it be resolved?
Given the failing IP address I'd say it was BLODA:
http://cygwin.com/faq/faq.using.html#faq.using.bloda
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/