From: "David S. Miller" <davem@davemloft.net>
To: drow@false.org
Cc: gdb@sources.redhat.com
Subject: Re: Unreasonable expectation in gdb.base/break.exp
Date: Tue, 04 Apr 2006 23:08:00 -0000 [thread overview]
Message-ID: <20060404.160901.88045460.davem@davemloft.net> (raw)
In-Reply-To: <20060404230535.GA13959@nevyn.them.org>
From: Daniel Jacobowitz <drow@false.org>
Date: Tue, 4 Apr 2006 19:05:35 -0400
> On Tue, Apr 04, 2006 at 04:02:27PM -0700, David S. Miller wrote:
> > I think this is perfectly reasonable and correct behavior on
> > both gdb's and gcc's part, and this check in break.exp should
> > be made a little bit more leanient.
> >
> > Any objections?
>
> That seems reasonable to me, but what do you propose testing for
> instead? I suppose if we don't check the source file, we'll still be
> able to check the function name when we hit the breakpoint.
The function name will be the inline function name, because
that is the function we will be "in", not main(). And that
could basically be anything.
Once you have inlining and optimizations enabled, this particular
check loses it's sense.
next prev parent reply other threads:[~2006-04-04 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 23:02 David S. Miller
2006-04-04 23:05 ` Daniel Jacobowitz
2006-04-04 23:08 ` David S. Miller [this message]
2006-04-04 23:12 ` Daniel Jacobowitz
2006-04-04 23:20 ` David S. Miller
2006-04-05 1:37 ` Daniel Jacobowitz
2006-04-05 5:11 ` David S. Miller
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=20060404.160901.88045460.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=drow@false.org \
--cc=gdb@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