[Discuss] segfault with cygwin

[John Blomfield]

pw wrote:
> Hello,
>
> I am running a bash script that iterates through
> a list of delimited ascii files and generates
> an output using the 'cut' command among others.
>
> The script appears to work just fine. It appears to consume
> 99% of my CPU and about 1.9 gigs of various memory.
>
> It generates the expected formatted outputs, but after
> a few files I get the following error and the shell cores:
>
>       2 [main] sh 1780 _cygtls::handle_exceptions: Error while dumping 
> state (probably corrupted stack)
> Segmentation fault (core dumped)
>
I don't know anything about cygwin but this appears to be an exception 
error "thrown" by the program due to trying to access a part of memory 
that is not defined.  Usually happens when you exceed the bounds of a 
defined memory area e.g. an array of bytes or refer to an address that 
is not allocated.  Probably a bug in cygwin or you have written 
something in bash script that writes stuff where you shouldn't.

John Blomfield
>
> I can restart the script on the file where it left off and it
> will process that file just fine, continue for a few files,
> and then core again.
>
> I am running bash in cygwin on Windows XP.
>
> Has anyone run into any similar errors using
> bash on cygwin? Any ideas?
>
> I have noted some oddities on this particular machine.
> It is a Dell Intel core2 Duo Precision 390 workstation
> with 2GB of ram. I am wondering if the problem is
> with core2 Duo MPU...
>
> Thanks for any clues,
>
> Peter
> _______________________________________________
> Discuss mailing list
> Discuss at vlug.org
> http://ladybug.vlug.org/cgi-bin/mailman/listinfo/discuss
>