From: Daniel Jacobowitz <drow@false.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: gdb@sources.redhat.com
Subject: Re: Unreasonable expectation in gdb.base/break.exp
Date: Wed, 05 Apr 2006 01:37:00 -0000 [thread overview]
Message-ID: <20060405013709.GA17095@nevyn.them.org> (raw)
In-Reply-To: <20060404.162052.87950568.davem@davemloft.net>
On Tue, Apr 04, 2006 at 04:20:52PM -0700, David S. Miller wrote:
> From: Daniel Jacobowitz <drow@false.org>
> Date: Tue, 4 Apr 2006 19:12:25 -0400
>
> > On Tue, Apr 04, 2006 at 04:09:01PM -0700, David S. Miller wrote:
> > > 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.
> >
> > Well, no, it shouldn't be. It should be some day, but for the moment,
> > gdb will report that you're in main no matter what's been inlined into
> > it.
>
> Indeed, you are right. I just rechecked exactly what happens
> and it does report "main ( ... ) at stdlib.h:333"
>
> So do you agree to change the check to just verify that we are
> in fact in main()?
Yes, I think so. I've had this failure in different compilers before.
Eventually, we'll have to relax the name check too, when we start
reporting inlined functions properly. But no one is working on that
right now; I had some patches to do it, but they were very buggy.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-05 1:37 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
2006-04-04 23:12 ` Daniel Jacobowitz
2006-04-04 23:20 ` David S. Miller
2006-04-05 1:37 ` Daniel Jacobowitz [this message]
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=20060405013709.GA17095@nevyn.them.org \
--to=drow@false.org \
--cc=davem@davemloft.net \
--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