Re: [RFA] gdb_continue_to_breakpoint

[Michael Snyder <msnyder@vmware.com>]

Daniel Jacobowitz wrote:
> On Thu, Sep 04, 2008 at 01:52:40PM -0700, Michael Snyder wrote:
>> This one-line change affects two changes that make
>> gdb_continue_to_breakpoint more useful.
>>
>> 1) If we accept "Breakpoint in" as well as "Breakpoint at",
>> then it will work for non-debug functions.
>>
>> 2) If we accept trailing text after the $location_pattern,
>> then we are not forced to include a location pattern that
>> takes us up to the end of the line.
>>
> 
>> 2008-09-04  Michael Snyder  <msnyder@vmware.com>
>>
>>       * lib/gdb.exp (gdb_continue_to_breakpoint): Accept "in" as well
>>       as "at" (for non-debug functions such as _start).  Also accept
>>       trailing text after $location_pattern.
> 
> I dunno - when we get symbol handling confused, e.g. we can find a
> minsym but not the full symbol, we tend to get the wrong output from
> breakpoint messages. 

Yabbut, this isn't a test of symbol handling, it's
a test of continuing to a breakpoint.

> For the second part can you just put the .* at
> appropriate callers?

Sure, if you prefer.  So maybe remove the .* but accept
the (in|at)?