Re: Updated cygwin dlls cause unnecessary reboot on NT

2006-12-25 Thread Christopher Faylor
On Tue, Dec 26, 2006 at 01:12:30AM -0500, Larry Hall (Cygwin) wrote: >On 12/25/2006, Linda Walsh wrote: >>FWIW, I have replaced the libs like cygwin1.dll, cygintl?.dll... and >>such while cygwin is running and not had a catastrophe as one might >>have trying to overwrite/update the memory image of

Re: Updated cygwin dlls cause unnecessary reboot on NT

2006-12-25 Thread Larry Hall (Cygwin)
On 12/25/2006, Linda Walsh wrote: FWIW, I have replaced the libs like cygwin1.dll, cygintl?.dll... and such while cygwin is running and not had a catastrophe as one might have trying to overwrite/update the memory image of a kernel dynamically, so I don't think it's quite all the end of the w

Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.

2006-12-25 Thread Larry Hall (Cygwin)
. Reformatted. andy wang wrote: Download a snapshot with symbols so you get better stack info: Either that, or build cygwin yourself with debugging info so you can do the same and play with the source. Thanks .Larry! If the b

Re: bash crashes after update

2006-12-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Serge Skorokhodov on 12/25/2006 5:48 PM: > Hi, > > I updated cygwin to the lates version on my WinXP SP2 notebook with > all recent updates and encounter a stopping problem. bash starts to > crash during setup script execution and cygwin

bash crashes after update

2006-12-25 Thread Serge Skorokhodov
Hi, I updated cygwin to the lates version on my WinXP SP2 notebook with all recent updates and encounter a stopping problem. bash starts to crash during setup script execution and cygwin does not work any more. Playing with the versions of cygwin1.dll etc. were no success. Does anybody encounter

select failed: Interrupted system call

2006-12-25 Thread andy wang
Hi, All: What's the reason can cause interrupted system call. the same program will not be interrupted running at linux. I know a singal can, Is there anything else can? Is there possible that pthread_cond_signal will do the same thing too? Regards, Andy -- Unsubscribe info: http://cygwin

spawn doesn't return for non-cygwin programs (and also is unbreakable)

2006-12-25 Thread Volker Quetschke
Hi! I recently tripped over the following problem: If a non-cygwin program gets started by cygwin's spawnvp() the spawn doesn't return until the started program returns. To illustrate the problem just compile attached the attached breaktestwin.c file as a cygwin executable $ gcc breaktestwin.c -

Re: Problems with bashrc in cygwin

2006-12-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Hyam Singer on 12/25/2006 12:26 PM: > I have installed cygwin and am having problems with my bashrc that I have > been unable to resolve. I am sure I must be missing something obvious, but > the source of the problem evades me. The most

Re: Updated cygwin dlls cause unnecessary reboot on NT

2006-12-25 Thread Linda Walsh
Igor Peshansky wrote: And that is exactly the problem -- not the .new suffixes. The way Cygwin is designed, you cannot have two versions of the Cygwin DLL (think of it as the kernel) in use at the same time, no matter what the name is. In Linux, you expect to reboot when upgrading the kernel --

Problems with bashrc in cygwin

2006-12-25 Thread Hyam Singer
I have installed cygwin and am having problems with my bashrc that I have been unable to resolve. I am sure I must be missing something obvious, but the source of the problem evades me. The most perplexing symptom I am experiencing is the following: If I include the following in my .bashrc:

Re: Updated cygwin dlls cause unnecessary reboot on NT

2006-12-25 Thread Igor Peshansky
On Mon, 25 Dec 2006, Linda Walsh wrote: > Larry Hall (Cygwin) wrote: > > What the file is named is insignificant. When the file is already in > > use, you will run into the situation where the newly installed file is > > not moved into place for use immediately . > --- >That is current cygwin

Re: "Command not found" error on gcc & v

2006-12-25 Thread andy wang
I think "+" sign is just say it is a directory like, not "seleced". If you want to install vi and gcc, please make sure the you click the "Skip" on the "New" column (with default view, it's the third column). then you can see the text change from "Skip" to "Keep" and the seond column will display

Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.

2006-12-25 Thread andy wang
Thanks .Larry! If the bug is not in the cygwin1.dll but an application and with stack corrupted, how can I using the low level debug technics to find the reason. Regards, Andy Download a snapshot with symbols so you get better stack info: Either that, or build c

"Command not found" error on gcc & vi

2006-12-25 Thread CHIAPOH TAI
I downloaded and installed "Cygwin DLL 1-5-23-2" yesterday onto my PC running Windows 2000 Professional. When I tried to type "vi" or "gcc" in Cygwin's window, I got bash: vi: Command not found bash: gcc: Command not found error messages. I thought I missed these packages, so I ran setup.e

Re: Updated cygwin dlls cause unnecessary reboot on NT

2006-12-25 Thread Linda Walsh
Larry Hall (Cygwin) wrote: What the file is named is insignificant. When the file is already in use, you will run into the situation where the newly installed file is not moved into place for use immediately . --- That is current cygwin behavior. It isn't required to be that way on NT.

Re: Updated cygwin dlls don't have the .dll extension; instead have .dll.new

2006-12-25 Thread Larry Hall (Cygwin)
Linda Walsh wrote: Eric Blake wrote: According to Charli Li on 12/24/2006 1:39 PM: Fishy enough, the new dlls had a filename extension of .dll.new Which means Windows is scheduled to rename it automatically at the next reboot, since it was in use at the time you ran setup.exe. Didn't

Re: how to debug with the crash especially with the corrupt stack in multi-thread environment using gdb.

2006-12-25 Thread Larry Hall (Cygwin)
andy wang wrote: Hi, All: now I get a new question: how to debug with the crash, especially with the corrupt stack in multi-thread environment using gdb. I found a related post using "info reg, watch 0x230" such low level command to trace a crash. http://www.cygwin.com/ml/cygwin/2004-02/msg

Re: perl script dies with The instruction at

2006-12-25 Thread moka
>How are you starting your script? Can you put: print "$^O: $]\n" >From the DOS prompt in the directory the script is in This says MSWIN32 Perl 5.008007 >or something at the beginning and verify for sure which perl you are using? Well, I unistalled all of cygwin and still got the same problem, so