Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 2 Jun 2004 12:55:41 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Wirawan Purwanto <wirawan AT camelot DOT physics DOT wm DOT edu>
cc: cygwin AT cygwin DOT com
Subject: Re: New cygwin1.dll (1.5.10-3) causes problem (hang) with gnuplot
In-Reply-To: <Pine.CYG.4.58.0406021203300.1768@wp>
Message-ID: <Pine.GSO.4.58.0406021254270.18478@slinky.cs.nyu.edu>
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0406021203300 DOT 1768 AT wp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine DOT GSO DOT 4 DOT 58 DOT 0406021254272 DOT 18478 AT slinky DOT cs DOT nyu DOT edu>
X-Scanned-By: MIMEDefang 2.39

On Wed, 2 Jun 2004, Wirawan Purwanto wrote:

> Hi, the new cygwin1.dll has caused a problem with gnuplot. Here are the
> version numbers (obtained via "cygcheck" command):
>
> cygwin                  1.5.10-3
> gnuplot                 3.8j.0-1
>
> What happens is that if you run the plot script (supplied in the
> attachment), the gnuplot program would just be stuck. Even pressing ^C
> doesn't stop the process (seems like all the keyboard is stuck). All I can
> do is to kill the gnuplot process from other cygwin window (or from Task
> Manager). I'm running cygwin under Windows 2000 SP 4 (build 2195).
>
> I'm not sure what kind of condition would trigger the problem. I
> haven't reduced the plot to see the exact cause of the "hang". The same
> script (offending3.plt), run in GNUPLOT version 3.7.2 under Red Hat Linux
> 8, does not cause this problem. Since this "hang" didn't happen with the
> previous version of cygwin1.dll, I report this as a cygwin bug first, to
> see if that's indeed the case. It may as well that this is gnuplot bug
> also.
>
> I tried to debug the program with gdb, here's the result:
>
> /d/temp $ gdb /usr/bin/gnuplot
> GNU gdb 2003-09-20-cvs (cygwin-special)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i686-pc-cygwin"...(no debugging symbols
> found)...
> (gdb) set args offending3.plt
> (gdb) run
> Starting program: /usr/bin/gnuplot.exe offending3.plt
> ---Type <return> to continue, or q <return> to quit---
> Showing multiplot
>
> Program received signal SIGSEGV, Segmentation fault.
> ---Type <return> to continue, or q <return> to quit---
> 0x7c5746b9 in KERNEL32!IsBadWritePtr () from /c/WINNT/system32/KERNEL32.DLL
> (gdb) where
> #0  0x7c5746b9 in KERNEL32!IsBadWritePtr () from /c/WINNT/system32/KERNEL32.DLL
                    ^^^^^^^^^^^^^^^^^^^^^^
This isn't your hang.  See
<http://cygwin.com/ml/cygwin/2004-06/msg00057.html>.
HTH,
	Igor

> #1  0x610a92ed in cygwin1!__getreent () from /usr/bin/cygwin1.dll
> #2  0x00000008 in ?? ()
> #3  0x0022d588 in ?? ()
> #4  0x610a9387 in cygwin1!__getreent () from /usr/bin/cygwin1.dll
> (gdb)

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/