Re: [patch/rfa] tweak patterns for annota3.exp

[Daniel Jacobowitz <drow@false.org>]

On Sun, Dec 05, 2004 at 06:56:45PM -0800, Randolph Chung wrote:
> > Are you sure there's nothing but an extra \r\n?  It definitely passes
> > for others, so I'd like to know where that came from.
> 
> yup... the log says:
> 
> signal SIGUSR1^M
> ^M
> ^Z^Zpost-prompt^M
> Continuing with signal SIGUSR1.^M
> ^M
> ^Z^Zstarting^M
> ^M
> ^Z^Zframes-invalid^M
> ^M
> ^Z^Zbreakpoint 2^M
> ^M
> Breakpoint 2, 0x000105d4 in handle_USR1 (sig=16) at /home/tausq/gdb/gdb-cvs/gdb/testsuite/gdb.base/annota3.c:18^M
> ^M
> ^Z^Zsource /home/tausq/gdb/gdb-cvs/gdb/testsuite/gdb.base/annota3.c:18:238:beg:0x105d4^M
> ^M
> ^Z^Zstopped^M
> ^M
> ^Z^Zpre-prompt^M
> (gdb) ^M
> ^Z^Zprompt^M
> PASS: gdb.base/annota3.exp: send SIGUSR1
> 
> i have no idea where that comes from either... 

You could put a breakpoint on vfprintf_unfiltered to find out :-)

> mmmmm. gcc creates this:
> 
> .globl handle_USR1
>         .type   handle_USR1, @function
> .LFB3:
>         .loc 1 18 0
> handle_USR1:
>         .PROC
>         .CALLINFO FRAME=64,NO_CALLS,SAVE_SP,ENTRY_GR=3
>         .ENTRY
>         copy %r3,%r1
> .LCFI0:
>         copy %r30,%r3
> .LCFI1:
>         stwm %r1,64(%r30)
> .LCFI2:
>         stw %r26,-36(%r3)
>         ldo 64(%r3),%r30
>         ldwm -64(%r30),%r3
>         bv,n %r0(%r2)
>         .EXIT
>         .PROCEND
> 
> we are breakpointing at the ldo insn, which seems to be correct from the
> prologue analysis point of view. do you mean that the ".loc" should be
> right before the ldo?

There should be an _additional_ .loc before the ldo.  The rule for what
GDB expects is: one line note before the function, one after the
prologue.

-- 
Daniel Jacobowitz