Re: your turn :-)

[Joel Brobecker <brobecker@gnat.com>]

> I'll see if I can take care of this. Right now, GDB is completely
> broken again. This change sort of patch things up a little bit
> by preventing a SEGV. But we get some other problems that just
> screw the testsuite run.

The first problem that I saw was the following. Using advance.exp:

        (gdb) b func
        Breakpoint 1 at 0x10001600: file advance.c, line 18.
        (gdb) run
        Starting program: /chico.a/brobecke/mips-inline/gdb-public/gdb/testsuite/gdb.bas
        e/advance 
        
        Breakpoint 1, func () at advance.c:18
        18        x = x + 5;
        (gdb) advance func3
        warning: GDB can't find the start of the function at 0x3.
        
            GDB is unable to find the start of the function at 0x3
        and thus can't determine the size of that function's stack frame.
        This means that GDB may be unable to access that stack frame, or
        the frames below it.
            This problem is most likely caused by an invalid program counter or
        stack pointer.
            However, if you think GDB should simply search farther back
        from 0x3 for code which looks like the beginning of a
        function, you can increase the range of the search using the `set
        heuristic-fence-post' command.
        zsh: 19433825 segmentation fault (core dumped)  ../../gdb advance

It turns out it was that heuristic_proc_desc problem I sent a patch for
striking again. Forgot to apply my patch before starting the testsuite
:-(.

-- 
Joel