Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Ben Pfaff <blp@cs.stanford.edu>
Newsgroups: comp.programming
Subject: Re: breakpoint blues
Date: Thu, 01 Nov 2012 14:09:37 -0700
Lines: 7
Message-ID: <871ugdjai6.fsf@blp.benpfaff.org>
References: <5285d664-6243-464e-a76c-cd4cdff6ec21@googlegroups.com>
Reply-To: blp@cs.stanford.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1351804178 9369 127.0.0.1 (1 Nov 2012 21:09:38 GMT)
X-Complaints-To: action@cs.stanford.edu
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Cancel-Lock: sha1:+zhcnKAf92NNYXv0pLH1o8cqLl4=
Xref: csiph.com comp.programming:2436

bob <bob@coolfone.comze.com> writes:

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

This sounds very toolchain and debugger dependent.