Re: [ANNOUNCEMENT] New package: S-Lang 2.2.2-2
On Mon, Nov 15, 2010 at 04:11:19PM +, Marco Atzeri wrote: > Hi, > S-lang library and shell are now available for cygwin. > The version 2.2.2-1 of > libslang2 > libslang-devel > slsh > have been uploaded. Thanks. This makes it easier to build "most," the pager program. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
mknetrel script
hi, How do I add CFLAGS=-DDEBUGGING to .mknetrel source file? Thx -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [mintty 0.9.2] cmd.exe history doesn't work properly
On 11/15/2010 1:39 PM, Patches Houlihan wrote: > Browsing through the command history in cygwin's cmd.exe access to the > Windows shell doesn't work properly in mintty. Instead of showing > previous commands, the up and down keys just move a cursor on the > screen. Using up/down works fine with bash on mintty and cmd.exe > works fine in the standard Windows console Cygwin terminal. It's a well-known problem: Cygwin pseudo-terminals look like pipes to Windows, so cmd thinks it's being run non-interactively. You have two solutions: 1) Use the "conin wrapper" around cmd to give the program a real terminal, or 2) Better yet, use "rlwrap cmd" so you get nice readline-based line editing and persistent history with cmd. (I still need to get around to packaging a newer version of rlwrap, but the current one should work fine for this purpose.) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[mintty 0.9.2] cmd.exe history doesn't work properly
Browsing through the command history in cygwin's cmd.exe access to the Windows shell doesn't work properly in mintty. Instead of showing previous commands, the up and down keys just move a cursor on the screen. Using up/down works fine with bash on mintty and cmd.exe works fine in the standard Windows console Cygwin terminal. mintty 0.92 CYGWIN_NT-6.1-WOW64 [...] 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Error in tcsh globing - take two
I originally sent this a bit over a month ago and have not received a rely. I just verified that the problem still exists. I also verified that the same tcsh version under Linux (Ubuntu 10.4) does not have the problem, so this looks like a Cygwin specific problem. With the latest tcsh and cygwin on a windows XP SP3 machine I'm seeing a problem with file globing. If you have a directory with three files tmp.c, vcd_priv.c and vcd_priv2.cc (just create them with touch). If you run ls *.cc it will display both vcd_priv.c and vcd_priv2.cc. The bash shell does not have this problem. Regards, Cary -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: whois-5.0.8-1
Version 5.0.8-1 of "whois" has been uploaded. Whois is a client for the whois directory service. It allows you to retrieve information on domains name, IP addresses, and more. If you're not sure what version do you have you can use the following command to both check version number and integrity of the install: % cygcheck -c whois *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Lapo Luchini -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ( Solved ) - RE: perl debugger v5.10.1 in CYGWIN_NT-5.1 1.7.7(0.230/5/3) 2010/-08-31 -- is hanging
2010/11/15 Justin Amburn: > Thank you Reini!! It was the PERLDB_OPTS in the Windows environment > variables that was preventing the debugger from initializing. Great > troubleshooting. I'm doing this professionally in real life :) Less stressful than coding. -- Reini Urban -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
( Solved ) - RE: perl debugger v5.10.1 in CYGWIN_NT-5.1 1.7.7(0.230/5/3) 2010/-08-31 -- is hanging
>RemotePort debugging? That looks now like a different problem. >I remember vaguely that this was just fixed recently. >Are you sure that you have a debug server running at port 2000? Looks like >ActiveState Perl Dev Kit uses such a beast, and therefore they cannot talk. >Do you really need that? (In only know komodo, mod_perl, Enbugger >injection) unset it if in doubt. Thank you Reini!! It was the PERLDB_OPTS in the Windows environment variables that was preventing the debugger from initializing. Great troubleshooting. Regards, Justin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sshd problem with recent snapshots
On Nov 15 11:40, Christopher Faylor wrote: > On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote: > >On 11/15/2010 11:09 AM, Corinna Vinschen wrote: > >> On Nov 13 10:00, Ken Brown wrote: > >>> On 11/5/2010 8:03 AM, Ken Brown wrote: > If I start sshd on a machine running a recent snapshot, I'm unable to > login to that machine via ssh. The connection is closed right after I > type my password. The problem first appears in the snapshot of > 20100917. To reproduce: > > 1. Start sshd. > > 2. While logged in as one user, try to login as another user. For > example: > > $ ssh kbrown-ad...@localhost > kbrown-ad...@localhost's password: > Connection to localhost closed by remote host. > Connection to localhost closed. > > The same thing happens if I try to ssh in from a different machine on > the network. > >>> > >>> Further information: There are two entries in the Windows Event > >>> Viewer (Application Log) after the failed login: > >>> > >>> sshd: PID 2264: Accepted password for kbrown-admin from ::1 port 1025 > >>> ssh2. > >>> > >>> sshd: PID 2264: fatal: chmod(/dev/tty1, 0622) failed: Permission denied. > >> > >> Hmm, that's weird. I'm using the latest Cygwin from CVS, and I cannot > >> reproduce this. I tried to login from a remote machine with pubkey and > >> password authentication using an admin account as well as a normal user > >> account. Works fine for me in all these cases. > >> > >> I can't quite believe it, but maybe that's OS related. I'm running my > >> tests on W7 in the first place. What OS are you using? > > > >XP SP3. > > FWIW, I couldn't duplicate this on XP SP3 but my ssh installation was a > little nonstandard. I ended up breaking ssh entirely over the weekend > so I'm looking for a random helpful blog to help me diagnose the > problem. > > But, seriously, I'll check this as soon as I get things back to a running > state. What I don't grok is that this should start with the 20100917 snapshot, but works with 20100912. There's nothing in the 09-17 ChangeLog which would be related. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New package: slrn-0.9.9p1-1
Hi,
slrn ('S-Lang read news') is now available for cygwin.
The version 0.9.9p1-1 has been uploaded.
DESCRIPTION
slrn ('S-Lang read news') is a newsreader, i.e. a program that accesses
a newsserver to read messages from the Internet News service (also
known as 'Usenet'). It runs in console mode. Beside the usual features
of a newsreader slrn supports scoring rules to highlight, sort or kill
articles based on information from their header. It is highly customizable,
allows free key-bindings and can easily be extended using the sophisticated
S-Lang macro language. Offline reading is possible by using either
slrnpull (shipped with slrn) or a local newsserver (like leafnode or INN).
HOMEPAGE
http://www.slrn.org/
Regards
Marco Atzeri
If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list,
look at the "List-Unsubscribe: " tag in the email header of this
message. Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that
is available starting at this URL.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New package: S-Lang 2.2.2-2
Hi, S-lang library and shell are now available for cygwin. The version 2.2.2-1 of libslang2 libslang-devel slsh have been uploaded. DESCRIPTION S-Lang is a multi-platform programmer's library designed to allow a developer to create robust multi-platform software. It provides facilities required by interactive applications such as display/screen management, keyboard input, keymaps, and so on HOMEPAGE http://www.s-lang.org/ Regards Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sshd problem with recent snapshots
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote: >On 11/15/2010 11:09 AM, Corinna Vinschen wrote: >> On Nov 13 10:00, Ken Brown wrote: >>> On 11/5/2010 8:03 AM, Ken Brown wrote: If I start sshd on a machine running a recent snapshot, I'm unable to login to that machine via ssh. The connection is closed right after I type my password. The problem first appears in the snapshot of 20100917. To reproduce: 1. Start sshd. 2. While logged in as one user, try to login as another user. For example: $ ssh kbrown-ad...@localhost kbrown-ad...@localhost's password: Connection to localhost closed by remote host. Connection to localhost closed. The same thing happens if I try to ssh in from a different machine on the network. >>> >>> Further information: There are two entries in the Windows Event >>> Viewer (Application Log) after the failed login: >>> >>> sshd: PID 2264: Accepted password for kbrown-admin from ::1 port 1025 ssh2. >>> >>> sshd: PID 2264: fatal: chmod(/dev/tty1, 0622) failed: Permission denied. >> >> Hmm, that's weird. I'm using the latest Cygwin from CVS, and I cannot >> reproduce this. I tried to login from a remote machine with pubkey and >> password authentication using an admin account as well as a normal user >> account. Works fine for me in all these cases. >> >> I can't quite believe it, but maybe that's OS related. I'm running my >> tests on W7 in the first place. What OS are you using? > >XP SP3. FWIW, I couldn't duplicate this on XP SP3 but my ssh installation was a little nonstandard. I ended up breaking ssh entirely over the weekend so I'm looking for a random helpful blog to help me diagnose the problem. But, seriously, I'll check this as soon as I get things back to a running state. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: tcsh cpp completion
On Nov 9 13:24, Daniel Schneider wrote:
> The default tcsh completion for g++ doesn't like .cpp files.
> /etc/profile.d/complete.tcsh
> ...
> complete g++ n/*/f:*.{C,cc,o,s,i}/
> complete CC n/*/f:*.{C,cc,cpp,o,s,i}/
>
> Why is "cpp" only for CC, but not g++?
The complete.tcsh file is the vanilla file from the upstream sources.
You should ask this upstream.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ioctl() on socket fd's take 3 seconds on 1.7.7
On Nov 9 09:20, Jason Curl wrote: > 166 65418 [main] ipcheck 5580 ioctl: fd 3, cmd 80087364 > --- Process 5580, exception C005 at 610C8C86 Crash in Cygwin, but the address doesn't help much, unfortunately. > Interestingly enough, the program works. That is, it finds all > interfaces and returns correct values (except interface names are > UUIDs instead of something more friendly like "eth0" that existed in > 1.5.26). For a reason. The UUID names are the only officially *unique* interface names available in Windows. The ethX names in Cygwin 1.5 were faked, based on the order in which the interfaces appear in a Windows call. This order is not guaranteed to stay intact during the uptime of a machine. Cygwin also provides an ioctl called SIOCGIFFRNDLYNAM, which provides the interface name shown in the Windows network adapter settings window. > My antivirus has been closed (not simply deactivated) with no change > in behaviour. > > It will be a little later when I'm able to generate a working test case. T'would be nice. Please make it short and simple and, if possible, in plain C. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sshd problem with recent snapshots
On 11/15/2010 11:09 AM, Corinna Vinschen wrote: On Nov 13 10:00, Ken Brown wrote: On 11/5/2010 8:03 AM, Ken Brown wrote: If I start sshd on a machine running a recent snapshot, I'm unable to login to that machine via ssh. The connection is closed right after I type my password. The problem first appears in the snapshot of 20100917. To reproduce: 1. Start sshd. 2. While logged in as one user, try to login as another user. For example: $ ssh kbrown-ad...@localhost kbrown-ad...@localhost's password: Connection to localhost closed by remote host. Connection to localhost closed. The same thing happens if I try to ssh in from a different machine on the network. Further information: There are two entries in the Windows Event Viewer (Application Log) after the failed login: sshd: PID 2264: Accepted password for kbrown-admin from ::1 port 1025 ssh2. sshd: PID 2264: fatal: chmod(/dev/tty1, 0622) failed: Permission denied. Hmm, that's weird. I'm using the latest Cygwin from CVS, and I cannot reproduce this. I tried to login from a remote machine with pubkey and password authentication using an admin account as well as a normal user account. Works fine for me in all these cases. I can't quite believe it, but maybe that's OS related. I'm running my tests on W7 in the first place. What OS are you using? XP SP3. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: tcsh out of memory?
On Nov 6 12:00, Jim Reisert AD1C wrote: > I just got an abort/out of memory error from tcsh. I was sourcing a > script to run telnet. Should I be worried about this? > > tcsh current memory allocation: > free: 0 10275 11 26830211 > 11000000000000 > 000 > used: 0 26 441 795 277 158 656 31 16 1031 > 26200000000000 > 000 > Total in use: 1344512, total free: 148480 > Allocated memory from 0x9a to 0x. Real top at 0xb0c800 > nbytes=65552: Out of memory > Abort (core dumped) That *might* indicate a Cygwin bug. The tcsh memory allocation is very sensitive to certain problems in Cygwin. Please try a recent Cygwin snapshot first: http://cygwin.com/snapshots/ If it still fails, please try to create a *minimal* testcase tcsh script which allows to reproduce the problem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: /dev/sda2 - Bad file descriptor error with mkfs.ext4 on cygwin
On Nov 6 10:08, Phani Deepak Parasuramuni wrote: > Hi, > > I am using Cygwin 1.7.7 on Windows 7. > > I have installed e2fsprogs-1.41.12 on cygwin. > > I have carved out a 10G partition in my harddisk using windows disk manager. > > My 'cat /proc/partitions' command also lists out my sda2 partition, so > I am sure that there is sda2 partition with 10G > > $ cat /proc/partitions > major minor #blocks name > 8 0 312571224 sda > 8 1 302083072 sda1 > 8 2 10484736 sda2 > > Now, I am trying to use mkfs.ext4 to create an ext4 file system on > this partition. > > This is the command I am using: > $/usr/sbin/mkfs.ext4 /dev/sda2 > > it fails with error message; > "mkfs.ext4: Bad file descriptor while trying to determine filesystem size" > > Any idea why it is happening so? UAC? You need to run an elevated shell to be able to write to disk partitions. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sshd problem with recent snapshots
On Nov 13 10:00, Ken Brown wrote: > On 11/5/2010 8:03 AM, Ken Brown wrote: > >If I start sshd on a machine running a recent snapshot, I'm unable to > >login to that machine via ssh. The connection is closed right after I > >type my password. The problem first appears in the snapshot of > >20100917. To reproduce: > > > >1. Start sshd. > > > >2. While logged in as one user, try to login as another user. For example: > > > >$ ssh kbrown-ad...@localhost > >kbrown-ad...@localhost's password: > >Connection to localhost closed by remote host. > >Connection to localhost closed. > > > >The same thing happens if I try to ssh in from a different machine on > >the network. > > Further information: There are two entries in the Windows Event > Viewer (Application Log) after the failed login: > > sshd: PID 2264: Accepted password for kbrown-admin from ::1 port 1025 ssh2. > > sshd: PID 2264: fatal: chmod(/dev/tty1, 0622) failed: Permission denied. Hmm, that's weird. I'm using the latest Cygwin from CVS, and I cannot reproduce this. I tried to login from a remote machine with pubkey and password authentication using an admin account as well as a normal user account. Works fine for me in all these cases. I can't quite believe it, but maybe that's OS related. I'm running my tests on W7 in the first place. What OS are you using? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Executable bit check
On Nov 5 14:47, Illia Bobyr wrote: > On 11/5/2010 11:56 AM, Eric Blake wrote: > > [...] > > On Linux: > > > > $ setfacl -m mask:rwx d/f > > $ getfacl d/f > > # file: d/f > > # owner: eblake > > # group: eblake > > user::rw- > > user:dummy:rwx > > group::rw- > > mask::rwx > > other::r-- > > > > $ chmod -x d/f > > $ getfacl d/f > > # file: d/f > > # owner: eblake > > # group: eblake > > user::rw- > > user:dummy:rwx #effective:rw- > > group::rwx #effective:rw- > > mask::rw- > > other::r-- > > > > Interestingly - that means that on Linux, chmod -x changed the mask > > entry of the ACLs, such that the effective permissions for the alternate > > user are no longer permitted; so even though user dummy has rwx ACLs, > > the mask prevents the user from executing the file any more. > > > > Cygwin does not emulate Linux in this regards at the moment, but now > > that you have pointed out a simple test case, it may be possible to > > patch cygwin1.dll to make the chmod() syscall affect the ACL mask as on > > Linux. That's very tricky. The chmod function only gets a new mode_t value which only applies to owner/group/others and the mask value. The mask value is changed by a chmod as well and non-default users and groups in the ACL are only affected indirectly by the mask value which results in effective permissions, as you can see above. And here's the problem: > It seems that setfacl also does not change the "mask" part on Cygwin: There's no equivalent for the Solaris/POSIX mask value in the Windows ACL. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to debug mintty or screen freeze
On 15 November 2010 10:25, Henry S. Thompson wrote: > Andy Koppe writes: > >> On 8 November 2010 10:15, Henry S. Thompson wrote: >>> Bear with me please, this is moderately complex: >>> >>> . . .the whole thing freezes solid. >>> >>> screen doesn't respond to escape commands, ~. does nothing, Control-C >>> has no effect, trying to close the window results in the "process not >>> responding" popup. >>> >>> It's not repeatable, in that reconnecting and changing to the same >>> gnus Subject buffer will succeed. >>> >>> I _presume_ some obscure character code is responsible. . . >>> >>> Two questions: >>> >>> 1) Anyone else seen anything like this? >> >> Not as such, but it could be to do with the following issue: if you >> cat a big file and press any key that sends a character, the terminal >> and cat will be deadlocked, like so: >> >> $ ps >> O 2408 1 2408 2408 ? 99498 12:27:13 /usr/bin/mintty >> O 2672 2772 2672 1580 5 99498 12:27:19 /usr/bin/cat >> >> They're both in write(), waiting for each other to read data from >> their side of the pty. Happens with all the pty-based terminals. >> Killing the cat resolves the deadlock, and the terminal merrily >> continues. > > OK, that's not it -- the ps output is > > 5712 1 5712 5712 ? 1003 16:09:26 /c/Cygwin/bin/mintty > 5748 5712 5748 5768 1 1003 16:09:26 /usr/bin/screen > 6036 5748 6036 6036 ? 1003 16:09:27 /usr/bin/screen > > and procexp shows mintty at 50% of the CPU, i.e. 100% of one of them. Shame. How come the mintty executable is shown as /c/Cygwin/bin/mintty rather than /usr/bin/mintty? Be careful in case there are multiple Cygwin DLLs involved. > Attaching with gdb shows > > #0 0x7c90120f in ntdll!DbgUiConnectToDbg () from > /c/WINDOWS/system32/ntdll.dll > #1 0x7c951e40 in ntdll!KiIntSystemCall () from > /c/WINDOWS/system32/ntdll.dll > #2 0x0005 in ?? () > #3 0x0004 in ?? () > #4 0x0001 in ?? () > #5 0x19c3ffd0 in ?? () > #6 0xba338548 in ?? () > #7 0x in ?? () > #8 0x7c90e920 in strchr () from /c/WINDOWS/system32/ntdll.dll > #9 0x7c951e60 in ntdll!KiIntSystemCall () from > /c/WINDOWS/system32/ntdll.dll > #10 0x in ?? () > > in thread 6 and > > #0 0x6110b348 in memcpy () from /c/Cygwin/bin/cygwin1.dll > #1 0x610f393a in dlrealloc () from /c/Cygwin/bin/cygwin1.dll > #2 0x58ca0008 in ?? () > #3 0x698f0008 in ?? () > #4 0x082fffe8 in ?? () > #5 0x0002 in ?? () > #6 0x0023c5bc in ?? () > #7 0xfffd in ?? () > #8 0x698f0008 in ?? () > #9 0x00506528 in ?? () > #10 0x0830 in ?? () > #11 0x698f0008 in ?? () > #12 0x0023c8d0 in ?? () > #13 0x61071218 in realloc () from /c/Cygwin/bin/cygwin1.dll > #14 0xfffd in ?? () > #15 0x005062a0 in ?? () > #16 0x000e in ?? () > #17 0x0009 in ?? () > #18 0x000f in ?? () > #19 0x005062a8 in ?? () > #20 0x0023c8d0 in ?? () > #21 0x00020500 in ?? () > #22 0x00506528 in ?? () > #23 0x000f in ?? () > #24 0x005062a8 in ?? () > #25 0x610c01a5 in _sigfe () from /c/Cygwin/bin/cygwin1.dll > #26 0x7475f1a6 in TF_InvalidAssemblyListCache () from > /c/WINDOWS/system32/MSCTF.dll > Cannot access memory at address 0x82fffec > > in thread 1 > > I expect those are no use. Not to me anyway, I'm afraid, but thanks for having a go. I assume you're using mintty-0.9.2 installed through setup.exe? Perhaps someone else has a better idea what do with the stackdumps then run them through 'addr2line -e mintty.exe', with mintty.exe built from the 0.9.2 sources with added -g and removed -s? > Should I try building a with-symbols version from source? Yes, please that give that a go. You can enable a debug build by putting 'debug=1' onto the make line. That will require the dmalloc library though. I'm afraid doing a release build with added debug symbols requires hacking the makefile: --- Makefile(revision 1077) +++ Makefile(working copy) @@ -32,8 +32,8 @@ cc_opts += -DDMALLOC -g ld_opts += -ldmallocth else -cc_opts += -DNDEBUG -fomit-frame-pointer -Os -ld_opts += -s +cc_opts += -DNDEBUG -fomit-frame-pointer -Os -g +ld_opts += endif Another thing you could try is to enable logging to a file using the --log command option. Perhaps that will show what control sequence triggers the problem. Obviously you'll want to remove any private details before sending the log. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygserver shuts down 'unexpectedly
On Oct 27 05:07, Jeff Rancier wrote: > Is there a timeout for cygserver? After running for a while, I get the > following > > in the terminal: > > $ cygserver: All pending requests processed > cygserver: No longer accepting requests - cygwin will operate in daemonless > mode > cygserver: All outstanding process-cache activities completed > cygserver: Shutdown finished. > > [1]+ Done/usr/sbin/cygserver -f /etc/cygserver.conf > --log-level 7 (wd: ~) > (wd now: /srv/www/htdocs) There's no timeout. Cygserver only shuts down if it gets one of the signals SIGHUP, SIGINT or SIGTERM, or if the shutdown message is send, for instance by using `cygserver -S'. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
R: mkshortcut missing from user guide
--- Lun 15/11/10, Nellis, Kenneth ha scritto: > To whom it may concern, mkshortcut is > missing from > the list of Cygwin utilities in the user guide. > http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html > --Ken Nellis > mkshortcut belongs to cygutils package The utilities reported on cygwin-ug-net.html are those included in the cygwin package, so only the core ones. Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
mkshortcut missing from user guide
To whom it may concern, mkshortcut is missing from the list of Cygwin utilities in the user guide. http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html --Ken Nellis
Re: How to debug mintty or screen freeze
Andy Koppe writes: > On 8 November 2010 10:15, Henry S. Thompson wrote: >> Bear with me please, this is moderately complex: >> >> . . .the whole thing freezes solid. >> >> screen doesn't respond to escape commands, ~. does nothing, Control-C >> has no effect, trying to close the window results in the "process not >> responding" popup. >> >> It's not repeatable, in that reconnecting and changing to the same >> gnus Subject buffer will succeed. >> >> I _presume_ some obscure character code is responsible. . . >> >> Two questions: >> >> Â 1) Anyone else seen anything like this? > > Not as such, but it could be to do with the following issue: if you > cat a big file and press any key that sends a character, the terminal > and cat will be deadlocked, like so: > > $ ps > O2408 12408 2408? 99498 12:27:13 /usr/bin/mintty > O267227722672 15805 99498 12:27:19 /usr/bin/cat > > They're both in write(), waiting for each other to read data from > their side of the pty. Happens with all the pty-based terminals. > Killing the cat resolves the deadlock, and the terminal merrily > continues. OK, that's not it -- the ps output is 5712 15712 5712? 1003 16:09:26 /c/Cygwin/bin/mintty 574857125748 57681 1003 16:09:26 /usr/bin/screen 603657486036 6036? 1003 16:09:27 /usr/bin/screen and procexp shows mintty at 50% of the CPU, i.e. 100% of one of them. Attaching with gdb shows #0 0x7c90120f in ntdll!DbgUiConnectToDbg () from /c/WINDOWS/system32/ntdll.dll #1 0x7c951e40 in ntdll!KiIntSystemCall () from /c/WINDOWS/system32/ntdll.dll #2 0x0005 in ?? () #3 0x0004 in ?? () #4 0x0001 in ?? () #5 0x19c3ffd0 in ?? () #6 0xba338548 in ?? () #7 0x in ?? () #8 0x7c90e920 in strchr () from /c/WINDOWS/system32/ntdll.dll #9 0x7c951e60 in ntdll!KiIntSystemCall () from /c/WINDOWS/system32/ntdll.dll #10 0x in ?? () in thread 6 and #0 0x6110b348 in memcpy () from /c/Cygwin/bin/cygwin1.dll #1 0x610f393a in dlrealloc () from /c/Cygwin/bin/cygwin1.dll #2 0x58ca0008 in ?? () #3 0x698f0008 in ?? () #4 0x082fffe8 in ?? () #5 0x0002 in ?? () #6 0x0023c5bc in ?? () #7 0xfffd in ?? () #8 0x698f0008 in ?? () #9 0x00506528 in ?? () #10 0x0830 in ?? () #11 0x698f0008 in ?? () #12 0x0023c8d0 in ?? () #13 0x61071218 in realloc () from /c/Cygwin/bin/cygwin1.dll #14 0xfffd in ?? () #15 0x005062a0 in ?? () #16 0x000e in ?? () #17 0x0009 in ?? () #18 0x000f in ?? () #19 0x005062a8 in ?? () #20 0x0023c8d0 in ?? () #21 0x00020500 in ?? () #22 0x00506528 in ?? () #23 0x000f in ?? () #24 0x005062a8 in ?? () #25 0x610c01a5 in _sigfe () from /c/Cygwin/bin/cygwin1.dll #26 0x7475f1a6 in TF_InvalidAssemblyListCache () from /c/WINDOWS/system32/MSCTF.dll Cannot access memory at address 0x82fffec in thread 1 I expect those are no use. Should I try building a with-symbols version from source? ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 651-1426, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
