Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: Multiple breakpoint locations
Date: Sun, 18 Nov 2007 01:32:00 -0000	[thread overview]
Message-ID: <18239.38458.695867.472660@kahikatea.snap.net.nz> (raw)
In-Reply-To: <u1waodgv7.fsf@gnu.org>

 > > The manual lists cases where a given function in source can correspond to
 > > several PC values, and they say:
 > > 
 > >         In all those cases, @value{GDBN} will insert a breakpoint at all
 > >         the relevant locations.
 > > 
 > > So it happens automatically.
 > 
 > Well, I think it's not explicit enough.  I will try to add some more
 > explicit explanations when I have time.

The only way I've managed to create breakpoints at multiple locations is
by specifying a line number inside the template/constructor.  For templates
I understand that the breakpoints are for different types, e.g., float, int
as used by the program.  For constructors:


   * For a C++ constructor, the GCC compiler generates several
     instances of the function body, used in different cases.

I don't understand what the second breakpoint refers to, or why there may
be more than one instance.

So I think, at some point, a separate node, or one grouped with breakpoint
menus to highlight the differences, would be a good idea.  Other things, like
needing to include the return type in the template name when specifying a
breakpoint location could also be included.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-11-18  1:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:15 Nick Roberts
2007-11-13 19:28 ` Vladimir Prus
2007-11-13 19:59   ` Daniel Jacobowitz
2007-11-13 20:09   ` Nick Roberts
2007-11-13 20:14     ` Daniel Jacobowitz
2007-11-13 20:18     ` Bob Rossi
2007-11-13 20:19     ` Vladimir Prus
2007-11-13 22:03     ` Andreas Schwab
2007-11-14  6:20       ` Vladimir Prus
2007-11-14 10:12         ` Andreas Schwab
2007-11-14 21:26           ` Jim Blandy
2007-11-14 21:34             ` Vladimir Prus
2007-11-14 22:08             ` Andreas Schwab
2007-11-15  4:08             ` Eli Zaretskii
2007-11-15 13:37               ` Daniel Jacobowitz
2007-11-15 16:50               ` Jim Blandy
2007-11-13 22:18   ` Eli Zaretskii
2007-11-13 23:39     ` Douglas Evans
2007-11-14  4:17       ` Eli Zaretskii
2007-11-14  5:02         ` Joel Brobecker
2007-11-14  6:13         ` Vladimir Prus
2007-11-14 18:54           ` Eli Zaretskii
2007-11-14 19:00             ` Vladimir Prus
2007-11-17 11:55 ` Eli Zaretskii
2007-11-17 12:07 ` Eli Zaretskii
2007-11-17 14:14   ` Vladimir Prus
2007-11-17 15:36     ` Eli Zaretskii
2007-11-18  1:32       ` Nick Roberts [this message]
2007-11-18  2:26         ` Daniel Jacobowitz
2007-11-18  8:47           ` Nick Roberts
2007-11-19 12:57             ` Daniel Jacobowitz

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=18239.38458.695867.472660@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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