Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.programming Subject: Re: breakpoint blues Date: Fri, 02 Nov 2012 21:00:18 +1300 Lines: 12 Message-ID: References: <5285d664-6243-464e-a76c-cd4cdff6ec21@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net l2YUg7rtAyEkl+6PQx1F7ApxK2LCuRyuo0PFPQaGQprnLd52PwYFU9dKlDEFtg46+8 Cancel-Lock: sha1:9H5eommxGeT0yCrGhkKTKfnOLLE= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:12.0) Gecko/20120423 Thunderbird/12.0 In-Reply-To: <5285d664-6243-464e-a76c-cd4cdff6ec21@googlegroups.com> Xref: csiph.com comp.programming:2437 On 11/02/12 09:51, bob wrote: > Has anyone else seen a lot of breakpoints that don't break when they get hit? > > Seems like it happens a lot with variable declarations. > > Makes programming a lot harder when you can't trust your breakpoints. If you are using your debugger as a programming tool rather than the last resort, you are going about things the wrong way. -- Ian Collins