X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <493BD69D.4040B992@dessent.net> Date: Sun, 07 Dec 2008 05:58:53 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gdb is sooooo slow - is that normal? References: <006101c95866$181d4650$4001a8c0 AT mycomputer> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 John Emmas wrote: > That shows 5 stages out of maybe 20 or so that seem to run before my own app > appears on screen. The problem is that each of those stages can take > anywhere from about 6 seconds up to 15 seconds (taking longer, the more > breakpoints I've set). Therefore after starting the debug process, it can > take between 2 minutes and maybe 6 minutes before my app gets launched. Is > this normal for Cygwin? The more complex the app, the worse the problem is. > If I set more than about 5 breakpoints with a complicated app, the debugger > takes so long to get going that it becomes not worth waiting. Does anyone > else find this? I'd like to find out whether it's a problem with Cygwin or > with CodeBlocks. No, that's certainly not normal. Try the same commands directly in Cygwin's packaged gdb with CodeBlocks completely removed from the picture and see if it's the same speed. Brian -- 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/