From: Amit Kale <amitkale@linsyssoft.com>
To: gdb@sourceware.org
Subject: Re: Breakpoints in constructors
Date: Mon, 26 Dec 2005 07:52:00 -0000 [thread overview]
Message-ID: <200512261322.29545.amitkale@linsyssoft.com> (raw)
In-Reply-To: <200512151935.54801.amitkale@linsyssoft.com>
Would you like us to rebase this patch to current cvs tree to make it easier
to review it?
-Amit
On Thursday 15 Dec 2005 7:35 pm, Amit Kale wrote:
> Hi,
>
> I am posting this on behalf of TimeSys Corporation. We had developed a fix
> (read hack) to enable gdb to place breakpoints in C++ constructors. This
> work was done on gdb 6.2 (patch attached).
>
> I was planning to post this patch after rebasing to current gdb, but then
> found that there was some communication on this earlier. I would like to
> know gdb guru's opinion on this patch. Does this appear to much of a hack?
> Someone else working on a better solution?
>
> Any help on this patch and/or directions for making this right will be
> highly appreciated.
> Thanks.
> -Amit
next prev parent reply other threads:[~2005-12-26 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 14:06 Amit Kale
2005-12-26 7:52 ` Amit Kale [this message]
2005-12-27 4:07 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2003-04-30 14:44 breakpoints " Michael Elizabeth Chastain
2003-05-01 2:13 ` Daniel Berlin
2003-04-30 4:36 Michael Elizabeth Chastain
2003-04-30 5:20 ` Daniel Berlin
2003-04-18 20:04 David Carlton
2003-04-24 14:50 ` Daniel Jacobowitz
2003-04-24 22:02 ` Paul Koning
2003-04-25 0:30 ` Daniel Jacobowitz
2003-04-29 20:45 ` Paul Koning
2003-04-29 21:24 ` Daniel Jacobowitz
2003-04-30 19:04 ` Michael Eager
2003-04-30 19:11 ` Paul Koning
2003-04-30 19:19 ` 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=200512261322.29545.amitkale@linsyssoft.com \
--to=amitkale@linsyssoft.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).