From: Amit Kale <amitkale@linsyssoft.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB patches <gdb-patches@sources.redhat.com>
Subject: Re: Breakpoints in constructors
Date: Fri, 06 Jan 2006 14:19:00 -0000 [thread overview]
Message-ID: <200601061948.57309.amitkale@linsyssoft.com> (raw)
In-Reply-To: <20060106134503.GB4796@nevyn.them.org>
On Friday 06 Jan 2006 7:15 pm, Daniel Jacobowitz wrote:
> On Fri, Jan 06, 2006 at 06:56:39PM +0530, Amit Kale wrote:
> > I was not able to fix other failures though. The major one being a
> > breakpoint on a statement in main causes three breakpoints to appear.
> > It's because this statement is a call to a C++ inlined function. The
> > expansion of inline function dodges the check in my patch for multiple
> > breakpoints appearing for the same C statement when the statement is
> > spread across multiple instructions interlaced with instructions from
> > surrounding statements. I checked for function name, which would be the
> > inline function name. That's why my check fails. Sigh, I wanted to send
> > this patch again only after fixing this problem, but don't have any good
> > ideas on how to do that. I'll very much appreciate if anyone has ideas
> > about fixing this.
>
> The hack of checking whether they appear in the same function just
> won't scale to fix this - possibly ever, but certainly not until inline
> functions are represented properly in GDB's symbol table.
Bad news.
Any ideas about how to check whether multiple functions appear in the same
function block?
-Amit
next prev parent reply other threads:[~2006-01-06 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 13:06 Amit Kale
2006-01-03 18:53 ` Eli Zaretskii
2006-01-06 13:28 ` Amit Kale
2006-01-03 19:40 ` Daniel Jacobowitz
2006-01-06 13:26 ` Amit Kale
2006-01-06 13:45 ` Daniel Jacobowitz
2006-01-06 14:19 ` Amit Kale [this message]
2006-01-06 14:25 ` 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=200601061948.57309.amitkale@linsyssoft.com \
--to=amitkale@linsyssoft.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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