Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 20 Sep 2001 17:07:20 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Help... GDB no longer works after updating... Message-ID: <20010920170720.A16816@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <30BDEE18E474D511BB0A00D0B7BB87AF0928DF@camel.mha.ca> <200109202041.NAA05602@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109202041.NAA05602@cygnus.com> User-Agent: Mutt/1.3.21i On Thu, Sep 20, 2001 at 02:42:11PM -0600, Mark Paulus wrote: >If you are having problems, and you can't debug gdb, then try this: > >Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option. Then when you >get your crash message, you should be able to go back to the map file, >and figure out which subroutine/code segment is causing the problem. >Then you might be able to either desk check the code slightly, or rerun >gdb on gdb, and dissassemble the subroutine in question. This should >allow you to get to the exact machine instruction, which will take you >back to the high level code involved, and then it's a matter of >figuring out which variable is whacked, or when/how the stack is >overflowing and whacking the code segment, etc, etc. You might also be able to use the techniques here: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/how-to-debug-cygwin.txt?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src to debug the application. This would require using an older cygwin1.dll that works, assuming that cygwin1.dll is the problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/