X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Trace:	112851081/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.17.75/None/johne53 AT tiscali DOT co DOT uk
X-SBRS:	None
X-RemoteIP:	79.66.17.75
X-IP-MAIL-FROM:	johne53 AT tiscali DOT co DOT uk
X-MUA:	Microsoft Outlook Express 6.00.2900.2180Produced By Microsoft MimeOLE V6.00.2900.2180
X-IP-BHB:	Once
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	AvAEAMdNO0lPQhFL/2dsb2JhbACDfFDHWYMF
X-IronPort-AV:	E=Sophos;i="4.33,728,1220223600"; d="scan'208";a="112851081"
Message-ID:	<006101c95866$181d4650$4001a8c0@mycomputer>
From:	"John Emmas" <johne53 AT tiscali DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
Subject:	gdb is sooooo slow - is that normal?
Date:	Sun, 7 Dec 2008 12:19:46 -0000
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I use an IDE called CodeBlocks to build and debug my Cygwin projects.  The
builds usually go okay but debugging is horrendously slow.  CodeBlocks has
a debugger output window which typically shows output like this (I assume
this is either what's being sent to gdb or what's getting returned) -

This GDB was configured as "i686-pc-cygwin".
>>>>>>cb_gdb:
> set confirm off
>>>>>>cb_gdb:
> set width 0
>>>>>>cb_gdb:
> set height 0
>>>>>>cb_gdb:
> set breakpoint pending on
>>>>>>cb_gdb:
> set print asm-demangle on

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.

Thanks,

John


--
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/

- Raw text -