X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A538D54.5090003@aim.com> Date: Tue, 07 Jul 2009 14:00:52 -0400 From: Mark Harig User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Questions about setting the CYGWIN env. variable's 'error_start' Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AOL-IP: 64.12.78.138 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Mon, 6 Jul 2009 11:21:14 -0400 , Christopher Faylor wrote: > For the curious, I debugged it by doing this: > > set CYWGIN=error_start:gdb > > When gdb popped up, the stack trace led me straight to the problem. > Thanks for the reminder. Here is the documentation for the 'error_start' option: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html or, http://cygwin.com/1.7/cygwin-ug-net/using-cygwinenv.html > |error_start:Win32filepath| - if set, runs |Win32filepath| when cygwin > encounters a fatal error, which is useful for debugging. > |Win32filepath| is usually set to the path to *gdb* or *dumper*, for > example |C:\cygwin\bin\gdb.exe|. There is no default set. Is there a canonical or recommended, robust method that should be used for setting 'error_start'? It appears that your method assumes the value of PATH is set appropriately. Is it recommended that users define the environment variable 'Win32filepath' to have the value of the Windows location of the desired debugger and, if so, can this be changed dynamically? (That is, if a user changes 'Win32filepath' at, say, a shell prompt, would this be picked up by 'error_start'?) And has the new 'insight' GUI included with 'gdb' been tested to work as a value for 'error_start'? -- 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