From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25342 invoked by alias); 24 Sep 2003 18:13:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 3197 invoked from network); 24 Sep 2003 17:41:51 -0000 Received: from unknown (HELO mail2.butlermfg.com) (12.13.78.38) by sources.redhat.com with SMTP; 24 Sep 2003 17:41:51 -0000 Received: from bmkc1svmail01.am.mfg ([]) by mail2.butlermfg.com (Merak 6.1.0) with ESMTP id DUO37460 for ; Wed, 24 Sep 2003 12:41:50 -0500 Received: by bmkc1svmail01.am.mfg with Internet Mail Service (5.5.2653.19) id ; Wed, 24 Sep 2003 12:40:50 -0500 Message-ID: <71A0F7B0F1F4F94F85F3D64C4BD0CCFE02BF255E@bmkc1svmail01.am.mfg> From: "Parker, Ron" To: cygwin@cygwin.com Subject: Debugging cygwin1.dll startup Date: Wed, 24 Sep 2003 18:13:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2003-09/txt/msg01543.txt.bz2 I have made some local changes to the source for cygwin1.dll and would like to debug it, as the first Cygwin process, bash, begins. I know about using a gdb-startup.cmd setup for JIT debugging applications, but this does not seem to work for debugging Cygwin prior to reaching a bash prompt. Is the 'dll cygwin1' GDB mechanism the only way to do what I need? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/