Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: kdsfinger@gmail.com
Cc: Jim Blandy <jimb@codesourcery.com>, gdb@sourceware.org
Subject: Re: gdb breakpoint problem
Date: Tue, 12 Jun 2007 11:19:00 -0000	[thread overview]
Message-ID: <20070612111935.GA29495@caradoc.them.org> (raw)
In-Reply-To: <cac7ac540706112033r1c94b2ebl4b0bbb1c0b338254@mail.gmail.com>

On Mon, Jun 11, 2007 at 11:33:15PM -0400, kdsfinger@gmail.com wrote:
> The breakpoints set at line 22, 23, 24 are all ignored. However, the
> breakpoints set at line 16, 17, 18 are all good to break the program.
> What's the difference? They are doing the same thing. Why gdb treated
> them differently? Thanks for your comments.

That's a known bug in GDB - it has trouble with the way GCC generates
constructors for C++ classes.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-12 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 17:00 kdsfinger
2007-06-11 17:22 ` Daniel Jacobowitz
2007-06-11 17:36 ` Jim Blandy
2007-06-11 20:21   ` Eli Zaretskii
2007-06-12  3:33   ` kdsfinger
2007-06-12 11:19     ` Daniel Jacobowitz [this message]
2007-06-12 11:29       ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070612111935.GA29495@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=kdsfinger@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox