X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <50E47C7B.3000104@cs.utoronto.ca> Date: Wed, 02 Jan 2013 11:29:15 -0700 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: bash problem after restarting computer (cygwin 1.7.17-1) References: <20130102182128.GA16844@ednor.casa.cgf.cx> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 02/01/2013 11:24 AM, Aaron Schneider wrote: > On 02/01/2013 19:21, Christopher Faylor wrote: >> But most likely you need to run rebaseall. > > It was solved with just restarting the computer. The Windows motto: "when in doubt, reboot" FYI, it may be that you just hit a mintty session that had a particularly fork-unfriendly address space layout. The fact that there were cygwin dlls lower than 0x400000 is especially suspicious. If it happens again, opening a new mintty window, from the shortcut, might work just as well as rebooting did. Ryan -- 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