Re: Improve end check on rs6000 prologue analyzer

[Daniel Jacobowitz <drow@false.org>]

On Wed, Oct 18, 2006 at 09:58:08PM +0200, Mark Kettenis wrote:
> Unfortunately, I still get a few regressions, see below.  They all
> seem to be problems with not skipping the complete prologue.  I get
> the feeling that using line number information for prologue skipping
> is just not reliable :(.

It's true that it isn't completely reliable, but it's usually "good
enough" and has its own advantages - it's better than accidentally
walking off into the epilogue, for instance, as this code is currently
somewhat prone to.

What version of GCC are you using?  Perhaps I can reproduce it with a
different version.

> @@ -9334,7 +9349,7 @@
>  PASS: gdb.gdb/selftest.exp: Set xgdb prompt
>  PASS: gdb.gdb/selftest.exp: send ^C to child process
>  PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process
> -PASS: gdb.gdb/selftest.exp: backtrace through signal handler
> +FAIL: gdb.gdb/selftest.exp: backtrace through signal handler
>  Running ../../../../src/gdb/gdb/testsuite/gdb.gdb/xfullpath.exp ...
>  PASS: gdb.gdb/xfullpath.exp: breakpoint in captured_main
>  PASS: gdb.gdb/xfullpath.exp: run until breakpoint at captured_main

This, though, I probably can't without access to an OpenBSD system...

-- 
Daniel Jacobowitz
CodeSourcery