Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Tue, 21 Mar 2000 10:19:42 -0500 To: Pavel Kudrna Cc: Sourceware Mail List , Insight Mail list Subject: Re: Problems with Insigt and cygwin1.dll Message-ID: <20000321101942.D18125@cygnus.com> Mail-Followup-To: cgf@cygnus.com, Pavel Kudrna , Sourceware Mail List , Insight Mail list References: <0a8701bf92be$66802960$0100000a@dualbeast> <200003210830.AAA25416@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003210830.AAA25416@cygnus.com>; from kudrna@plasma.troja.mff.cuni.cz on Tue, Mar 21, 2000 at 09:29:34AM +0100 On Tue, Mar 21, 2000 at 09:29:34AM +0100, Pavel Kudrna wrote: >I have also the unresolved problem with crash of another program in >_size_of_stack_reserve__ (). So I can help with the fact that this >function you can find in ld.exe. But also I have to repeat your >(maybe not expressed) question how to debug into the .dll? Can >anybody at least say that it's not possible? I answered this question in the cygwin mailing list. The bottom line is that, yes, it is, of course, possible to debug any DLL. You can load a DLLs symbols via the "add-symbol" command or you can set a breakpoint in your program after the DLL has been loaded and set breakpoints and debug normally. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com