Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <001301c07d3f$34d79850$0200a8c0@voyager> From: "Trevor Forbes" To: "Cygwin" Subject: Debugging cygwin1.dll Date: Sat, 13 Jan 2001 18:26:42 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 I have tried to debug cygwin1.dll with limited success. I am able to trace the source through the cygwin1.dll until "gdb itself" just stacks dumps with an access violation which then just reloads gdb (error_start). I have gdb and a debug cygwin1.dll in the same directory but not in my path. I run GDB from cmd.exe and then load the program under test and set the breakpoints as usual. Is there a more reliable method of debugging the cygwin1.dll? Would I be better to remotely debug cygwin from my Linux box? Is there any gdb stub to achieve this? Any pointers would be appreciated. Regards Trevor -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple