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: Wed, 05 Apr 2006 05:11:00 -0000 [thread overview]
Message-ID: <20060404.221022.131097924.davem@davemloft.net> (raw)
In-Reply-To: <20060405013709.GA17095@nevyn.them.org>
From: Daniel Jacobowitz <drow@false.org>
Date: Tue, 4 Apr 2006 21:37:09 -0400
> On Tue, Apr 04, 2006 at 04:20:52PM -0700, David S. Miller wrote:
> > 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.
Ok, I'll cook up a patch that does this.
Thanks.
prev parent reply other threads:[~2006-04-05 5:11 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
2006-04-05 5:11 ` David S. Miller [this message]
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.221022.131097924.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