[ANNOUNCEMENT] [SECURITY] Updated: mintty-0.9.8-1

2011-05-20 Thread Andy Koppe
mintty 0.9.8-1 is on its way to the Cygwin mirrors. CHANGES === - Fixed a security issue with the OSC 701 sequence for setting and querying the terminal's locale, which allowed an arbitrary string (not including line endings) to be set as the locale and then echoed back as if typed by the user

RE: Executing a basic program

2011-05-20 Thread Agnelomaria
Thank you .. I will try asking others Buchbinder, Barry (NIH/NIAID) [E] wrote: > > Agnelomaria wrote on Friday, May 20, 2011 10:11 PM > >> I am just learning to program in C++. > > I couldn't help you if I wanted to, but you are > off topic for this list. You might look elsewhere, > becaus

RE: Executing a basic program

2011-05-20 Thread Buchbinder, Barry (NIH/NIAID) [E]
Agnelomaria wrote on Friday, May 20, 2011 10:11 PM > I am just learning to program in C++. I couldn't help you if I wanted to, but you are off topic for this list. You might look elsewhere, because, from past experience I doubt anyone here will help. Just wanting to save you some time. Good lu

Executing a basic program

2011-05-20 Thread Agnelomaria
Hi, I am just learning to program in C++ . I am following a book called Exploring C++ . The first task is to execute the code which I will paste below. I have compiled the code . I tried executing the code using ./a.exe command but the code does not seem to terminate. I have no idea what the cod

Re: mk_all

2011-05-20 Thread Kenneth Wolcott
On Fri, May 20, 2011 at 13:09, kathy3826 wrote: > > >No, my guess is that you used mk_all when you should have used ./mk_all > >and that shows the real problem. > > > That wasn't the problem. Wow, this has been a very interesting detective puzzle game, a bit more difficult than "Twenty Questions"

Re: mk_all

2011-05-20 Thread kathy3826
>No, my guess is that you used mk_all when you should have used ./mk_all >and that shows the real problem. That wasn't the problem. -- View this message in context: http://old.nabble.com/mk_all-tp31655700p31665937.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Chris Sutcliffe
An additional crash (attempting to load a torrent) now gives the following: Program received signal SIGABRT, Aborted. 0x77aef8c1 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/system32/ntdll.dll (gdb) bt #0 0x77aef8c1 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Chris Sutcliffe
On 20 May 2011 13:44, Christopher Faylor wrote: > On Fri, May 20, 2011 at 01:38:42PM -0400, Chris Sutcliffe wrote: >>No luck with 0x00405AA8, but it could be in libtorrent.dll, which I >>will also build with debugging info.  I did manage to find the >>following (after loading the cygwin1.dbg symbol

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Christopher Faylor
On Fri, May 20, 2011 at 01:38:42PM -0400, Chris Sutcliffe wrote: >On 20 May 2011 13:15, Christopher Faylor wrote: >> On Fri, May 20, 2011 at 12:51:24PM -0400, Chris Sutcliffe wrote: >>>On 20 May 2011 01:44, Christopher Faylor wrote: On Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wro

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Chris Sutcliffe
On 20 May 2011 13:15, Christopher Faylor wrote: > On Fri, May 20, 2011 at 12:51:24PM -0400, Chris Sutcliffe wrote: >>On 20 May 2011 01:44, Christopher Faylor wrote: >>> On Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wrote: Creating a debug build hasn't helped either. ?When it crashes

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Christopher Faylor
On Fri, May 20, 2011 at 12:51:24PM -0400, Chris Sutcliffe wrote: >On 20 May 2011 01:44, Christopher Faylor wrote: >> On Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wrote: >>>Creating a debug build hasn't helped either. ?When it crashes it's >>>causing a stack dump, so doing a 'bt' in gdb

Re: Issues with latest rtorrent under Win7 x64 when attempting to package

2011-05-20 Thread Chris Sutcliffe
On 20 May 2011 01:44, Christopher Faylor wrote: > On Thu, May 19, 2011 at 10:01:47PM -0400, Chris Sutcliffe wrote: >>Creating a debug build hasn't helped either.  When it crashes it's >>causing a stack dump, so doing a 'bt' in gdb just returns 'no stack'. > > That probably means that it's forking.

Re: mk_all

2011-05-20 Thread René Berber
On 5/20/2011 3:50 AM, kathy3826 wrote: > it must have been make all. And it seems I can bypass the one with x windows > using source code. No, my guess is that you used mk_all when you should have used ./mk_all and that shows the real problem. -- René Berber -- Problem reports: http://

Re: Disabling /etc/profile.d/bash_completion.sh restored my sanity!

2011-05-20 Thread Christopher Faylor
On Fri, May 20, 2011 at 12:36:00PM +0200, Jan Bruun Andersen wrote: >Bash was driving me crazy with extremely slow completion of directory >and filenames. I looked at all possible options to mount, I >practically nuked my PATH to make no network was involved, I looked >for stuff to add to CYGWIN. F

Disabling /etc/profile.d/bash_completion.sh restored my sanity!

2011-05-20 Thread Jan Bruun Andersen
Bash was driving me crazy with extremely slow completion of directory and filenames. I looked at all possible options to mount, I practically nuked my PATH to make no network was involved, I looked for stuff to add to CYGWIN. Finally I found this little nugget of gold: http://cfc.kizzx2.com/index.

Re: mk_all

2011-05-20 Thread kathy3826
Thanks guys, it must have been make all. And it seems I can bypass the one with x windows using source code. -- View this message in context: http://old.nabble.com/mk_all-tp31655700p31662386.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http:/

Re: -a $HOME/.bashrc and -a ~/.bashrc produce different results

2011-05-20 Thread Csaba Raduly
On Thu, May 19, 2011 at 11:06 PM, Eric Blake wrote: > "$HOME" expands $HOME, but "~/.bashrc" does _not_ expand ~.  For > tilde-expansion to occur, it must be unquoted. Not only that, it has to be the first character: 3.5.2 Tilde Expansion - If a word begins with an unquoted