This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Unreasonable expectation in gdb.base/break.exp


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]