Re: New cygwin1.dll (1.5.10-3) causes problem (hang) with gnuplot

On Wed, 2 Jun 2004, Igor Pechtchanski wrote: > On Wed, 2 Jun 2004, Wirawan Purwanto wrote: > > > 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) [snip] > > (g

New cygwin1.dll (1.5.10-3) causes problem (hang) with gnuplot

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

Re: Problem with noninteractive bash initialization

On Wed, 19 Nov 2003, Igor Pechtchanski wrote: > Don't know, WFM: > > $ echo '#!/bin/bash > echo "Hellow"' > xyz > $ bash -x xyz > + echo Hellow > Hellow > $ bash --version > GNU bash, version 2.05b.0(1)-release (i686-pc-cygwin) > Copyright (C) 2002 Free Software Foundation, Inc. > $ > > BTW, the

RE: Problem with noninteractive bash initialization

03, Morche Matthias wrote: > Dunno where Your read, but the document You referenced says: "When an > interactive shell that is not a login shell is started, Bash reads and > executes commands from `~/.bashrc', if that file exists." > > matthias > > &g

Problem with noninteractive bash initialization

Hi, How should a noninteractive bash begin (i.e. for executing a script)? Should bash read init files like ~/.bashrc, ~/.bash_profile, or /etc/profile? According to bash documentation on http://www.gnu.org/manual/bash-2.05a/html_mono/bashref.html#SEC62 , NO initialization files would be read

Cygwin-ssh under Windows 2000 + NTFS

Hi, Background: I put the latest cygwin on my Windows 2000 machine. The harddrive is using NTFS, and I run myself as a "restricted user". My home directory is /home/wirawan (a mounted dir somewhere), and the Administrator's directory is /home/Administrator. Now the problem: When I tried to run

The -a options no longer accessible in gcc 3.2?

I tried out the new gcc 3.2 from cygwin's website. But when I tried to generate the basic block information (-a options), cc1plus screams: unrecognized option `-a'. Why is this? Is it because this profiling is turned off, somehow? Thanks, Wirawan Note: please include my address also in the reply

Re: Strange behavior of MSVC's printf under cygwin shell?

Well, finally I figured out why the printf text is not displayed right away. You need to turn off the "tty" switch in CYGWIN enviroment variable: set CYGWIN=notty (under DOS prompt, or in autoexec.bat), before starting the bash. Wirawan -- Unsubscribe info: http://cygwin.com/ml/#unsubscri

Strange behavior of MSVC's printf under cygwin shell?

Hi, Why does the screen output displayed using MSVC's printf subroutine not get shown immediately under Cygwin shell (bash, specifically)? Rather, it would wait for a long time before showing the text lines (many lines at once). How to change this behavior? I used the following (simple) code as