From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [0/9] Breakpoints at multiple locations
Date: Fri, 07 Sep 2007 22:18:00 -0000 [thread overview]
Message-ID: <001601c7f19d$084b98c0$18e2ca40$@u-strasbg.fr> (raw)
In-Reply-To: <200709080011.13700.vladimir@codesourcery.com>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: Friday, September 07, 2007 10:11 PM
> To: gdb-patches@sources.redhat.com
> Subject: [0/9] Breakpoints at multiple locations
>
>
> At the moment, gdb assumes that a code breakpoint has
> a single PC value. One case where it does not work
> is C++ constructors -- GCC generates several function
> bodies, and GDB sets breakpoint on just one of them,
> so breakpoints in constructors don't work reliably.
> Another case is C++ templates -- if I set a breakpoint
> on a line in template function, there's unbounded number
> of template instantiations that have this line, but GDB
> cannot set breakpoints on all of them.
Another case is pascal (and probably other languages) that
allow overloading of functions, i.e. to implement several flavors
of a same name function, differing by their parameters.
So I will be most happy about this change inside gdb.
Pierre Muller
Pascal language maintainer.
next prev parent reply other threads:[~2007-09-07 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 20:11 Vladimir Prus
2007-09-07 22:18 ` Pierre Muller [this message]
2007-09-08 11:57 ` Eli Zaretskii
2007-09-08 14:32 ` Vladimir Prus
2007-09-08 16:27 ` Nathan J. Williams
2007-09-08 16:40 ` Vladimir Prus
2007-09-08 16:52 ` Daniel Jacobowitz
2007-09-10 4:47 ` Markus Deuling
2007-09-10 7:44 ` Vladimir Prus
2007-09-10 14:11 ` Markus Deuling
2007-09-10 15:38 ` Vladimir Prus
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='001601c7f19d$084b98c0$18e2ca40$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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